Chihab Otmani

Thanks for reporting that @stephane-tessier. Could you please confirm that you don't have any issues with type checking on your editor nor when using CLI commands (ng serve...)?

The only way I see to make it work with tsc is to update the tsconfig files generated by the CLI, something like `types: []` in `tsconfig.json` but not sure...

Could you please put the build outputs with and without `@ngx-env/builder` here?

Thanks for confirming the issue @jperezruiz. I was able to reproduce it on v11 with v1.1.0. I am looking into it.

Is it a project from scratch? If not could you please try to reproduce you error in a project from scratch? ``` npx @angular/cli@11 new ng-app11 cd ng-app11 && npx...

Hi @hmendezm, did you run `ng add @ngx-env/builder` to install and setup the package? If so, could you please copy paste your `angular.json`? Every builder property should have its value...

Hey @akshay-sf, Thanks a lot for you feedback! I haven't read the docs enough but it seems that dotenv-extended imposes some rules on your .env files which might not be...

Could you elaborate on why you would not use it ? Would you use the query component in React ? My understanding is like it is an anti-pattern to use...

I've just released a package that should help with the setup. https://www.npmjs.com/package/@dotenv-run/jest-angular Could you please give it a try?

Hello, You cannot achieve what you want. The plugin replaces process.env / import.meta.env notations in your code source with the values in your environment (including those read from you .env)...