commonjs output clashes with chunk splitting

[garthk]

Bug report

What is the current behavior?

Attempting to use optimization.splitChunks.cacheGroups in combination with commonjs results in broken output packages, importing of which fails with:

TypeError: Cannot read property 'call' of undefined
    at __webpack_require__ (/Users/garthk/src/webpack-4-bug/build/index.js:20:30)

If there's a documented way to get the entry bundle build/index.js to inhale the split bundle build/vendors.js so its imports don't fail, please let me know where it is and I'll file a PR to make it easier to find.

If the current behavior is a bug, please provide the steps to reproduce.

git clone https://github.com/garthk/webpack-4-chunk-splitting-bug.git
cd webpack-4-chunk-splitting-bug
cat README.md
npm install
node_modules/.bin/webpack
node -p 'Object.keys(require("./build"))'

Note error:

/Users/garthk/src/webpack-4-bug/build/index.js:20
/******/ 		modules[moduleId].call(module.exports, module, module.exports, __webpack_require__);
                              ^

TypeError: Cannot read property 'call' of undefined
    at __webpack_require__ (/Users/garthk/src/webpack-4-bug/build/index.js:20:30)

(modules has keys ./src/index.ts, crypto, tty, and util, and we're trying to find a moduleId of ./node_modules/uuid/index.js in there. No wonder it's failing. Anyhow; comment out the splitChunks block in webpack.config.js, try again, and note no error.

What is the expected behavior?

Being able to split the output into multiple files and require the entry point without failure.

Other relevant information:

webpack version: 4.8.3
Node.js version: 8.11.2
Operating System: macOS, Linux
Additional tools: none

[sokra]

target: "node" doesn't support splitChunks with chunks: "initial" or chunks: "all".

[alexander-akait]

@sokra maybe we can output warning on this?

[ooflorent]

@evilebottnawi It's a good idea. Also the documentation should be updated to reflect this limitation.

[webpack-bot]

This issue had no activity for at least half a year.

It's subject to automatic issue closing if there is no activity in the next 15 days.

[webpack-bot]

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.