-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Ship flat bundles instead of a lib folder #1359
Comments
Nice 👍. The angular team also ships their libs as FESM (Flat ES Modules). Here's the spec they use: https://docs.google.com/document/d/1CZC2rcpxffTDfRDs6p1cfbmKNLA6x5O-NtkJglDaBVs Also gave a talk about it last week: https://youtu.be/K4YMmwxGKjY. Maybe it helps 🙂 |
Interesting how the bundle winds are blowing, but the reasons mentioned in the linked article are sound, it was an interesting read. Am I right in that this won't start the es module export at all? @mxstbr what are you looking for as a first step regarding this? |
I don't know how to start this off to be honest @GGAlanSmithee. I guess a good first step would be to look at Reacts rollup config and figure out the parts that are related to the flat CJS bundles? We already use rollup to create our |
Going to prepare a PR for this. |
Amazing @Andarist, can't wait! 😍 |
I can work on closure if you like. |
Based on this blogpost by the React core team we should ship flat bundles instead of the
lib
folder we have right now. Essentially, rather than shipping tons of files we'd only ship two bundles that contain the CommonJS code.This will make it possible for us to experiment with Google Closure Compiler, ref #1360.
The text was updated successfully, but these errors were encountered: