Chihab Otmani

I get your point. The current implementation does not permit it for sure. But that could be nice feature indeed. What would be the best developer experience in your opinion?

I've published a new version of the package in alpha supporting runtime environment variables. I'd appreciate if you can give it a try. `npx ng add @ngx-env/builder` Set the `runtime`...

Added experimental runtime support in 17.3.0.

Closing the issue as this way for old v11 versions. Let me know if you still have it with newer Angular versions.

If you have a process is not defined you probably don't have the .env.d.ts file in your source folder. This file is created by running `ng add @ngx-env/builder`. Depending on...

Closing the issue, let me know if you still have it.

The package has been moved to devDependencies so it should not bother you anymore. Closing the issue, let me know if you still encounter it.

@andrevenancio could this package help? [@dotenv-run/cli](https://github.com/chihab/dotenv-run) ```sh /workspace apps frontend1 .env.local # API_USERS=http://localhost:3001/users src/ .env.dev # API_BASE=https://dotenv-run.dev .env.prod # API_BASE=https://dotenv-run.app .env # API_USERS=$API_BASE/api/v1/users API_AUTH=https://$API_BASE/auth package.json turbo.json ``` ```sh $> cd...

I wonder if invoking a script using `npx @componizer/run-schematics` that would `npx ng g @componizer/schematics` inside the project would work?

> the schematics needs to depend on schematics and not the ng-cli-schematics. You mean the "..extension depend on schematics..." here right? Is there a way to use schematics as a...