Tom Ohms
Tom Ohms
I agree with all the others. Not using **server.ts** while running serve is pointless. Still I didn't want to do without Angular 17, as there are a couple of new...
> @Tom4U You can update to v17 and use either the `browser` or the `browser-esbuild` builders. Both work like before. Yes, I know, thank you. But this would lead to...
> CalromEmailReportExtension Thank you very much for your time and work!
While trying to reproduce it on a new workspace I've noticed the following: **Using `tag1, tag2`** * @nx/web:application **no error, but only first tag is used** * @nx/js:library **no error,...
Much better from my point of view would be marking completed tasks with strike-through formatting (if possible) and even move them at the end of tasks. Maybe support for collapsing...
I definitely still like to see that feature :)
Maybe it will be enough to update MongoConnectionOptions. But I have not done any development in this project yet and don't know it for sure. But if no one else...
> The `package.json#config` [example](https://github.com/npm/cli/issues/8153#issuecomment-2718906990) is exactly how you want to do this. Those aren't parsed as "npm" config values, those are isolated as "user space" config values for the package....
I guess I have to clarify my use case here and I cannot see any solution to this. Here's how I use custom arguments in one of my NPM scripts:...
> `cross-env PROJECT=app1 npm run serve` works fine on all platforms, and env vars have always been accessible inside npm scripts. True, but that's not the same as extending existing...