Repository navigation
Add exports field to package.json - #7307
Merged
Merged
Conversation
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.
Closes #6258
Ref #5291
This Pull Request is necessary for Conditional exports (ESM and CJS).
Note: For backward compatibility, we may need to export
stylelint/lib/utils/*files.The following script can easily output many
lib/utils/settings.Script
I'd like to hear feedback about exporting
lib/**files. Should we export all files? I worry about frequent breaking changes in the future, if we exposed all modules (including internal ones).Ideally, we should export utilities only through
stylelint.utils, but actually we don't. Especially,isStandardSyntax*utilities are necessary to write a plugin or a custom rule.