Skip to content
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

feat: support package exports and custom paths #679

Open
wants to merge 1 commit into
base: bundlephobia
Choose a base branch
from

Conversation

KaelWD
Copy link

@KaelWD KaelWD commented Aug 14, 2022

Requires pastelsky/package-build-stats#52

fixes #218
fixes #379

Next step would be to parse package.exports and generate a list of available entrypoints and their sizes, probably have to skip anything with wildcards though.

@kurtextrem
Copy link

@pastelsky any updates here?

@radist2s
Copy link

radist2s commented Jul 7, 2024

@KaelWD, thank you so much for putting together this PR.
@pastelsky, this PR is quite important in my opinion, for example, my library doesn't display the bundle size even though it's done according to the standards. The reason for this is the absence of module and main in package.json, which is not a problem for modern Node.js (>12.x).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for multiple entry points with "exports" feature: alternate package entry points
4 participants