You can use dotenv package for this purpose. npm install dotenv –save After installing the package, add this in the top of your config: const webpack = require(‘webpack’); // only add this if you don’t have yet // replace accordingly ‘./.env’ with the path of your .env file require(‘dotenv’).config({ path: ‘./.env’ }); then in plugins … Read more
I had a similar error but for me it was react-router. Solved it by installing types for it. npm install –save @types/react-router Error: (6,30): error TS7016: Could not find a declaration file for module ‘react-router’. ‘\node_modules\react-router\index.js’ implicitly has an ‘any’ type. If you would like to disable it site wide you can instead edit tsconfig.json … Read more
Turned out to be an issue with Webpack just not resolving an import – talk about horrible horrible error messages 🙁 // I Had to change: import DoISuportIt from ‘components/DoISuportIt’; // to (notice the missing `./`) import DoISuportIt from ‘./components/DoISuportIt’;
You cannot use a variable as argument to require. Webpack needs to know what files to bundle at compile time. As it does no program flow analysis, it can’t know what you pass to the function. In that case it might be obvious, but this could go as far as using user input to decide … Read more
There are several way to approach globals: 1. Put your variables in a module. Webpack evaluates modules only once, so your instance remains global and carries changes through from module to module. So if you create something like a globals.js and export an object of all your globals then you can import ‘./globals’ and read/write … Read more