-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: packageJson.exports.types
should be always be ordered first
#294
Comments
PRs welcome! |
@keithamus would the PR include these changes?
Let me know if I missed anything in the outline 😄 if not, it should be a straightforward fix |
That’s correct. We use semantic versioning so prefixing your commit |
If we are doing this, should we also enforce the |
@keithamus are you still working on this? If not, I might pick it up. |
I am happy to accept PRs. I no longer contribute code to this repo as I prefer to let the community do so. |
Apologies, I meant to tag @jlarmstrongiv! I assume that this is not being worked on though? |
Failing Example:
More specifically,
Should be the first in the object as required by TypeScript.
according to publint.dev:EXPORTS_TYPES_SHOULD_BE_FIRST
Ensure types condition to be the first. The TypeScript docs recommends so, but it's also because the exports field is order-based.
For example, a scenario where both the types and import condition could be active, types should be first so that it matches and returns a .d.ts file, rather than a .js file from the import condition.
The text was updated successfully, but these errors were encountered: