dotenv-webpack not working. env file not loaded. variables are undefined

[wibed]

using esm module based project

{
  "start": "npm run clean && cross-env NODE_ENV=development NODE_OPTIONS=\"--loader=ts-node/esm --trace-warnings\" webpack serve --mode=development --config webpack.config.ts"
}

dotenv-webpack does not prevent the app from starting, any env variable ends up beeing undefined.
other plugins work as expected, thats why i dont assume my webpack.config.ts to be wrong

i load it as usual
as new Dotenv() entry in the plugin section:

...
import Dotenv from 'dotenv-webpack'
...
  plugins: [
    miniCSSPlugin,
    copyPlugin,
    htmlPlugin,
    forkCheckerPlugin,
    new Dotenv()
  ],
...

[TranquilMarmot]

Running into this as well; it seems like it's not loading the .env file no matter what I try

[cosi-conda]

Have you tried this?

package.json:
"build:local": "webpack --mode development --env NODE_ENV=local",

webpack config:

module.exports = async (env, options) => {
...

      new DotenvWebpackPlugin({
        systemvars: true,
        path: `./env/.env.${env.NODE_ENV}` // This means the env files are in a folder called `env` at the root
      }),

[wibed]

for me this is not working right.

i had some success installing process, but it remained empty even after setting up
ProvidePlugin, further specifying process: process/browser

accessible but remained empty. the path was set up as explained above.

[mrsteele]

The problem might be legitimate. I don’t have a lot of experience with module npm support. Anyone else here able to check out my code to see what’s going on?

also, if anyone has a simplified boilerplate here I could download that and give it a try.