dotenv-webpack
dotenv-webpack copied to clipboard
mrsteele
A secure webpack plugin that supports dotenv and other environment variables and only exposes what you choose and use.
I'm basically new to webpack and node, and I can't seem to make dotenv-webpack work when using webpack-merge. My webpack config files are in 3 separate files (webpack.common.js, webpack.prod.js, and...
Use `compiler.webpack.DefinePlugin` instead of require from webpack, this is also available way in webpack, and can be compatible with rspack. This can also avoid requiring wrong webpack when using monorepo...
using esm module based project ```json { "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...
What is the difference between using strings and variables when configuring path for dotenv-webpack?
1. Use variable mode ------------ const common = require("./webpack.common.js") const { merge } = require("webpack-merge") const DotEnv = require("dotenv-webpack") const webpack = require("webpack") const DotenvPath = `.env.${process.env.NODE_ENV}` console.log(DotenvPath) // .env.dev...
we are still on version 2 and out there is version 5 + it is causing usage of old dotenv so just nice to have latest versions :)) https://github.com/mrsteele/dotenv-webpack/blob/97a864d72302d25fad0cef618fcd3f09e94bc4e4/package.json#L54 ```...
Bumps [webpack](https://github.com/webpack/webpack) from 5.73.0 to 5.76.0. Release notes Sourced from webpack's releases. v5.76.0 Bugfixes Avoid cross-realm object access by @Jack-Works in webpack/webpack#16500 Improve hash performance via conditional initialization by @lvivski...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [json5](https://github.com/json5/json5) from 2.2.1 to 2.2.3. Release notes Sourced from json5's releases. v2.2.3 Fix: [email protected] is now the 'latest' release according to npm instead of v1.0.2. (#299) v2.2.2 Fix: Properties...
For CI purposes, I would like to expose some environment variables as defaults to webpack without exposing _all_ environment variables.
This is weird behaviour, espically because i have .env.defaults. starting my application failed if .env is not exist. Why it is strictly needed, if i do not want to include...
