Add 'version' property on Plugin type #4771
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Description
Checking the version of a fellow plugin is a common task in inter-plugin communication scenarios - as an example,
@rollup/plugin-commonjs
checks what version of@rollup/plugin-node-resolve
is present:This works because
@rollup/plugin-node-resolve
has an unofficialversion
field added to it. This PR just proposes to make this property official (and discoverable for Intellisense users) by adding aversion?: string
property to theOutputPlugin
type.The docs are updated accordingly.