Should list of node packages to transpile be whitelisted for performance?

[justin808]

Has anybody checked if Babel transpiling almost all packages in node_modules slows compilation times significantly?

I just noticed that the default config has a loader that compiles almost all of node_modules:

https://github.com/rails/webpacker/blob/master/package/rules/node_modules.js

  include: /node_modules/,
  exclude: /(?:@?babel(?:\/|\\{1,2}|-).+)|regenerator-runtime|core-js|^webpack$|^webpack-assets-manifest$|^webpack-cli$|^webpack-sources$|^@rails\/webpacker$/,

I see that a few packages are excluded.

Would it be preferable to have some configuration, maybe in config/webpacker.yml that white lists the packages to transpile?

[jakeNiemiec]

@justin808 First off, please see a wider discussion on this here: #2131 (comment)

Has anybody checked if Babel transpiling almost all packages in node_modules slows compilation times significantly?

Not only is it slower, it causes stack overflows and out of memory issues for many users. Again, see the issue above.

[nicospz]

Something like are-you-es5 can help you check what files need transpilation, then you include them using the regex string it generates
/node_modules/(?![plugin-1|plugin-2])/

[justin808]

Seems fixed by https://github.com/rails/webpacker/pull/2624/files.