Lars Gyrup Brink Nielsen

TypeScript 4.6 is incompatible with older versions of Angular such as the one used in this repository. See https://gist.github.com/LayZeeDK/c822cc812f75bb07b7c55d07ba2719b3.

Also, only use this starter repo for Angular v4 or v5. Library projects have been built in to Angular CLI since version 6 if I recall correctly.

Use: - Node.js 6.17.1 - npm 3.10.10 (I prefer [Volta](https://volta.sh) to manage Node.js versions) Then modify `package.json#devDependencies`: ```pwsh "@types/node": "~6.0.46", "browser-sync": "~2.12.12", "lite-server": "~2.2.2", ``` Finally: ```pwsh npm install npm...

Building on the existing documentation example here. Might not be 100% accurate as I'm writing the code from memory. # Using standalone pipe ```ts import { ComponentStore, tapResponse } from...

See [RFC: Add "ngrxOnInitStore" lifecycle method to ComponentStore (#3335)](https://github.com/ngrx/platform/discussions/3335) for a library hook proposal that might support other techniques.

@timdeschryver I suggest you mention ComponentStore in the title of this issue to avoid confusion with NgRx Effects.

> Instead of mentioning all of them, I think that we should try to standardize one of these. Definitely. Besides gaining knowledge of available techniques, this is the reason for...

> I think the trigger$/source$ is the most natural way. Also, that approach is used in the docs already. The standalone pipe technique additionally works well for parameterized effects. I...

> I have a related question: Is the generic type for `effect` always required? Effects without parameters require then the generic type `void`? If we leave out the generic, the...

> you could do something like this with a single operation (e.g. mergeMap): To me, `this.effect(mergeMap(v => doSomeStuff))` is closer to `this.effect(pipe(mergeMap(v => doSomeStuff)))` than `this.effect(trigger$ => trigger$.pipe(mergeMap(v => doSomeStuff)))`....