Chihab Otmani

``` npm create @angular ng-app-18 cd ng-app-18 && npx ng add @ngx-env/builder # add `console.log(import.meta.env.NODE_ENV)` to app.config.ts NODE_ENV=dev npm start ``` You should see dev displayed in the console. If...

You're right @bitbangx, for now, the runtime option has only been implemented for application and browser-esbuild builders. Update: Webpack support is soon to be added (next release v19)

v19 published, feel free to give it a try.

Thanks for raising the point. I'll see if I can make import.meta available for v14 and v15 too

Will close the issue as most of the downloads are for version > 16

Sure! That'd be super cool to see the package featured in dotenv docs

What version of the package are you using please?

The environment follows this rule: ```ts process.env.NG_APP_ENV || // @deprecated process.env.NODE_ENV || // default in @dotenv-run/core builderConfiguration // the angular build configuration ``` Example: if you set NODE_ENV the builder...

> Expected `MY_SECRET=prod` (which is defined in `.secrets.prod`) but got `MY_SECRET=dev` (which is defined in `.secrets`) I guess here MY_SECRET is rather defined in one of the `.env.*` files which...