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

Tracker for Bundler Support #24

Open
balupton opened this issue May 8, 2019 · 0 comments
Open

Tracker for Bundler Support #24

balupton opened this issue May 8, 2019 · 0 comments

Comments

@balupton
Copy link
Member

balupton commented May 8, 2019

This issue will serve to track bundler support for the editions field. If the bundler directly supports the editions field, then the autoloader can be successfully bypassed, and the optimal edition can be used for the bundler's requirements.

Why should bundlers support editions? Because the editions autoloader gets installed 800k times a week, and 4m times a month, and is used by over 100 packages. Plus, because editions allows the bundler to utilise the optimal edition for its use case, hence why editions exist in the first place - so the optimal edition is used for the user and bundler.

Learn more about editions.

Supported

  • browserify - already partially supported as it uses the browser field

Underway

  • pika - already partially supported as it uses the module field
    • boundation generates compatible editions support for it automatically

Not Yet Implemented

Reported Bundler Issues

Post the issue on the bundler requesting editions support, referencing this issue, and I will add it here.

Reported User Issues

Other references

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

No branches or pull requests

1 participant