pfeileon
pfeileon
In my case it only happens very rarely. Atm I have this issue with a test for an onPush component with MatTabGroupHarness. (OnPush doesn't actually matter.)
> The upgrade to npm 7 should have been a breaking change. 😢 Not only that, it shouldn't happen at all as long as NPM 7 is not part of...
When you have sub-projects and execute a complex npm script e.g. `cd projects/demo && npm run build` from your root folder and `npm run build` executes `npx ../whatever` on a...
> @pfeileon Could you elaborate on the last point > > > It's impossible to run ng e2e in a CI environment without also pointlessly starting the dev-server. > >...
``` // component @Component({ selector: 'app-test', template: 'test works!\n', styleUrls: ['./test.component.scss'], standalone: true, imports: [CommonModule] }) export class TestComponent { // doesn't matter if it's timer (one-off) or interval readonly...
@mlc-mlapis That is a valid reason; it should still be explicitly pointed out in the documentation. As is, the "Tour of Heroes"-doc is misleading. That's why I suggested adding a...
@ericmartinezr The documentation is still not correct: >When you provide the service at the root level, Angular creates a single, shared instance of HeroService and injects into any class that...
@yogeshgadge s. https://github.com/angular/angular-cli/issues/26718
Actually (at least in my experience), any input while running `podman-compose` causes the shell to brick. I need to start another instance to call `podman compose down`.
I am not sure if this shouldn't be its own issue (maybe a feature request) but `dependsOn` completely ignores additional sources, too: Properties mapped by these are always set in...