Clarify nodeModules loader in CHANGELOG.md

[oleksii-leonov]

New nodeModules loader significantly change behavior.
It's specified in Breaking changes section but description is quite small.
This PR adds more details to CHANGELOG.md about nodeModules loader and receipt to keep previous behavior.

[gauravtiwari]

thanks :)

[olimart]

Hi @aleksejleonov . Where are we supposed to insert snippet?
The following has no effect.

const { environment } = require('@rails/webpacker')

// https://github.com/rails/webpacker/issues/1892
environment.loaders.delete('nodeModules');

module.exports = environment

Raises

ERROR in ./app/javascript/packs/application.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
TypeError: [BABEL] /scaffold/scaffold/app/javascript/packs/application.js: (0 , _semver(...).coerce) is not a function (While processing: "/scaffold/babel.config.js$0")

[oleksii-leonov]

Hi @olimart!

It should be inserted into config/webpack/environment.js.

Also, more detailed description in v4-upgrade guide https://github.com/rails/webpacker/blob/master/docs/v4-upgrade.md#excluding-node_modules-from-being-transpiled-by-babel-loader.

But due to error description, looks like you issue not related to nodeModules loader.

TypeError: [BABEL] /scaffold/scaffold/app/javascript/packs/application.js: (0 , _semver(...).coerce) is not a function (While processing: "/scaffold/babel.config.js$0")

It may be related to broken config in application.js or babel.config.js files.

Also, after applying changes to babel.config.js or config/webpack/environment.js it may be helpful to restart rails and webpack-dev-server and clean cached assets with rm -r tmp/cache/webpacker public/packs public/packs-test.

[olimart]

Thanks @aleksejleonov will investigate further 👍