feat(node-resolve): expose plugin version

[lukastaegert]

Rollup Plugin Name: node-resolve

This PR contains:

• bugfix
• feature
• refactor
• documentation
• other

Are tests included?

• yes (bugfixes and features will not be merged without tests)
• no

Breaking Changes?

• yes (breaking changes will not be merged unless absolutely necessary)
• no

If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.

List any relevant issue numbers:
#1038

Description

In the course of #1038, we discovered that we actually can have a peer-dependency-like situation between the commonjs plugin and the node-resolve plugin: If the new commonjs version is used together with a node-resolve version older than 13.0.6, then we would like to throw an error.

Unfortunately while it is easy to discover that the node-resolve plugin is used by inspecting build options, it is close to impossible to discover its actual version.

This PR does something very simple: It fetches the plugin version from the package.json file and attaches it as a version property to the plugin so that other plugins can inspect it.

This could serve as a pattern for other plugins as well. E.g. I am also attaching a version property to the commonjs plugin in #1038.

To ease the release of #1038, I would see having something like this in node-resolve as blocking for the release of #1038. If we want to recommend this pattern to others, I am also considering to include a recommendation in the "plugin communication" section of the official Rollup docs.

[tjenkinson]

Lgtm

[lukastaegert]

Checking the version with the newly released plugin it turns out that the published version is always one release behind. E.g. @rollup/plugin-node-resolve@13.1.0 reports to have version 13.0.6 and 13.1.1. is reported as 13.1.0. The reason is that the last build of the plugin occurs before the version is incremented.

@shellscape the easiest possible way to address this is to add a "prebublish": "pnpm build" script to the node-resolve package.json file. This script would indeed run after the version is increased. Do you see any issues with that? Then I would create a small PR.

[shellscape]

You'll want prepublishOnly but that should work

[lukastaegert]

Ah you are right, forgot that prepublish does not do anything what you would expect it to do.

[shellscape]

For this use case, would this suffice?

const { version } = require('./package.json');
module.exports = { version };

Would save you a build step.