I acknowledge there should be a "module" like in the bower.json, I just wasn't able to find out how to do it..

I think no way tree-shaking, because it has been bundled into a pack.

Is this something that is being considered? I believe it would make sense to have an es module included in the final package

I'd hope to. It's only little more than a POF on my part, but I'd like to receive some feedback, especially on adoptability.

I think no way tree-shaking, because it has been bundled into a pack.

It should work because Webpack will modify bundle exports so that unused (i.e. not imported by some other module) parts of the code are not exported anymore, and then it will be cleaned up by "dead code elimination" after minification with Uglify/Babili (see https://webpack.js.org/guides/tree-shaking/ for details). That's why ES build should contain untranspiled imports/exports – it can be statically analyzed and modified.

I've been waiting for modular ImmutableJS so long ❤️ 🙏

@deepsweet Webpack can tree-shaking three.js?

@Shyam-Chen theoretically yes, it includes a "module" attribute in its package.json, and uses rollup.

If I understand correctly, the only 2 practical differences here is using export syntax instead of module.exports = syntax, and this is a non-minified source?

Seems fine to me.

I'm really curious how well this will work! I noticed code like mixin(...) in Collection.js, any fuction calls that run at module load time will be considered as possible side effect code and can't be tree shaken.

I will take a look at the effect next week or so.

@leebyron Are there any instructions on how to use this new es-module? I'm not getting any benefits in build after the update. I haven't modified the way I import immutableJS in the codebase. It could also be something related to my Webpack config. Therefore some light on how to benefit from this would be nice

@inakianduaga it should be noticeable only with minified builds because it relies on "dead code elimination". have you checked your final .min.js files?

also you can take a closer look at Immutable.js in your bundle, it should contain special "unused harmony export" comments made by Webpack for stuff you have never used. example.

@deepsweet Yeah, this was for minified files. I will check the webpack comments on the bundle. BTW, do you have a rough estimate of the reduction in size? I'm using list/map/records and nothing else from the library.

I'm also using Typescript which last time I looked recently didn't play so nicely with tree shaking, so that might be another thing

I haven't checked it by myself yet, but it depends on Immutable.js internals – if list/map/records are using 90% of the entire library then you'll get that 90% in your bundle. And if so then it requires another PR to reduce amount of internal cross-dependencies when it's possible.

I'm using list/map/records and nothing else from the library.

That's about 95% of the library :) - You're not likely to see much reduction

I just installed v4.0.0-rc.9, but dist/immutable.es.js isn't in the node_modules directory, any idea why?