dzintars
commented
4 years ago Major issue was related to webpack-merge package, which was resolved by maintainer by releasing 5.1.0 version of the package.
Dev version is running with warnings:
» yarn start
(node:12242) [MODULE_NOT_FOUND] Error: webpack-cli tried to access ts-node, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:12242) [MODULE_NOT_FOUND] Error: @types/webpack-dev-server tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: webpack-merge tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: webpack-merge tried to access @types/webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: @types/html-webpack-plugin tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: @types/mini-css-extract-plugin tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: @types/optimize-css-assets-webpack-plugin tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: @types/terser-webpack-plugin tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: @types/webpack-cleanup-plugin tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(node:12242) [MODULE_NOT_FOUND] Error: @types/webpack-merge tried to access webpack, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
⚠ ｢wds｣: HTTP/2 is currently unsupported for Node 10.0.0 and above, but will be supported once Express supports it
ℹ ｢wds｣: Project is running at https://0.0.0.0:3000/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /home/dzintars/code/github.com/dzintars/front
ℹ ｢wds｣: 404s will fallback to /index.html
(node:12242) [MODULE_NOT_FOUND] Error: @redux-saga/types tried to access redux, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
ℹ ｢wdm｣: wait until bundle finished: /
ℹ ｢wdm｣: Hash: c1bb7f17e96b6684b8ec
Version: webpack 4.43.0
Time: 6963ms
After installing fresh OS it is good moment to test all the latest and greatest packages. Most likely it will lead to some incompatibilities, but IMO it is worth to go thru the setup process again to refresh the memory/knowledge.