Conflict with block-scoped @types/node on env.d.ts about ngx-env HOT 5 CLOSED

the only error I found is when I run ng run my-project:server because there is types: [ 'node'] in the tsconfig.server.json file so it conflicts the exact same way.
I solved it by adding "skipLibCheck": true, in the compilerOptions of the tsconfig.server.json file.

Also, I think tsc --noEmit --skipLibCheck && eslint . --ext js,ts --quiet --fix is better than specifying the types

from ngx-env.

Not sure what you mean.

In my package.json I have:

    "@types/jasmine": "3.10.2",
    "@types/luxon": "2.0.7",
    "@types/node": "16.11.10",

So in tsconfig.json I tried to force jasmin and luxon:

  "types": ["luxon", "jasmine"],

but it didn't solve the problem.

BUT if I declare the types directly in the cli args, it seems to do the trick 🥳

tsc --noEmit --types jasmine,luxon && eslint . --ext js,ts --fix

It will do for now.
But if you have a cleaner solution let me know!
Thanks.

from ngx-env.

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...)?

from ngx-env.

Yes, I can confirm that. Everything works fine except the tsc cli

from ngx-env.

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 if that's the best/ a viable solution.

from ngx-env.