Update type definitions #161
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shellscape
approved these changes
Jan 13, 2020
shellscape
changed the title
|
Thanks for the PR. We need to get one more pair of eyes on this and we'll be good to merge. |
NotWoods
approved these changes
Jan 13, 2020
|
I'll get this published this week. |
LarsDenBakker
pushed a commit
to LarsDenBakker/plugins
that referenced
this pull request
Sep 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rollup Plugin Name:
jsonThis PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Description
The type definitions don't match the docs, or the plugin behavior. When used with TypeScript, you can't call the plugin without explicitly including these options which are meant to be optional. And
namedExports: falsewas literally not allowed.