Answer to own question! Spoiler: false. module.exports = { devtool: isProd ? false : ‘source-map’, } In Webpack 4 it was possible to value this with an empty string. webpack 5 is more strict. Webpacks devtool configuration.
Update 2021, Feb 25 Html-webpack-plugin v5 is released, just run npm i -D html-webpack-plugin@latest or npm uninstall html-webpack-plugin npm i -D html-webpack-plugin Original answer This is mostly related to html-webpack-plugin, and while its new version 5 (integrated with webpack v5) is still in beta, you should update it manually: npm show html-webpack-plugin version 4.5.1 npm … Read more
I had the exact same issue as the OP (@toge) having migrated from Webpack 4 to 5. Whilst I was looking to implement the solution posted by @seanbun, I came across the following setup for the new Webpack 5 asset modules config that allowed me to get both my previous file-loader svgs and font files … Read more
Change the following import { version } from ‘../../package.json’; to something like import packageInfo from ‘../../package.json’; And then change your access from something like version, or version: version, to version: packageInfo.version, As noted in the comments, there may be cases where you do not want to expose your entire package.json file in the client code.