Ok so I found the solution here. Basically, had to add 2 things to the webpack config under module.rules: { test: /\.m?js/, type: “javascript/auto”, }, { test: /\.m?js/, resolve: { fullySpecified: false, }, },
You can pass mode param in the webpack config or cli command. Config: mode: ‘development’ or mode: ‘production’ CLI: webpack –mode development or webpack –mode production
Go to the project and run below two commands npm install sass-loader -D npm install node-sass -D
I see you have three questions here; 1. What is tree shaking? 2. What’s the need of it? 3. And, how do you use it? 1. What’s tree shaking? Tree shaking refers to dead code elimination. It means that unused modules will not be included in the bundle during the build process. When we import … Read more
Try adding declare var require: any; on top.
You can make use of ref and ReactComponent named export when importing SVG file. Note that it has to be ref in order for it to work. The following examples make use of React hooks which require version v16.8 and above. Sample Dynamic SVG Import hook: function useDynamicSVGImport(name, options = {}) { const ImportedIconRef = … Read more
I had the same issue, this is the working solution i found on git hub. https://github.com/ChainSafe/web3.js/issues/4070 run in your project directory: npm install crypto-browserify stream-browserify assert stream-http https-browserify os-browserify tsconfig.json Add this in:”compilerOptions”: { […] } “paths” : { “crypto”: [“./node_modules/crypto-browserify”], “stream”: [“./node_modules/stream-browserify”], “assert”: [“./node_modules/assert”], “http”: [“./node_modules/stream-http”], “https”: [“./node_modules/https-browserify”], “os”: [“./node_modules/os-browserify”], }
If you store the path in a variable then IgnorePlugin will not work. Though you still could do: const myCustomModule = eval(‘require’)(myCustomPath)
Question: It feels like workaround, but isn’t there a more convenient way to handle such issues? I just pretend there will be more and more untransformed packages outside in the near future (following this discussion) and do we always have to manually put the package names for it in webpacks’ exclude rule?? You can use … Read more
Try this; you might be making wrong template path : new HtmlWebpackPlugin({ template: resolve(__dirname, ‘src/public’, ‘index.html’), filename: ‘./index.html’ }), If public is in src folder this should work It’s my assumption. Let me know if the issue still persists.