Issue after migrating Angular CLI to NX: NgRx/Signals store error

[alcaidio]

Hi everyone,

I recently migrated my project from Angular CLI to NX, and I've started encountering some strange errors with the NgRx/Signals store that I didn't have before. Specifically, I'm seeing the following error:

Argument of type 'unknown' is not assignable to parameter of type 'WritableStateSource<object>'.ts(2345)
or 
Exported variable 'UserStore' has or is using name 'SIGNAL' from external module "project/node_modules/@angular/core/index" but cannot be named.ts(4023)
⚠ Error (TS4023) Exported variable UserStore has or is using name SIGNAL from external module 

I've attached screenshots of the error and relevant code sections. Has anyone experienced similar issues or know what might be causing this after the migration? Any guidance on how to resolve it would be greatly appreciated!

Thanks in advance for your help!

PS: v18.2.0 for ANgular and @ngrx/signals

[brandonroberts]

#4151

[rainerhahnekamp]

@alcaidio are you accessing the SignalStore from an Nx Lib, right? Can you show a screenshot from the place you export it and where you use it?

[alcaidio]

Yes it's on Nx, but its' just side effect errors... Thanks @rainerhahnekamp

[alcaidio]

Edit: Maybe it was a side effect linked to lint/build errors that had not been resolved in a number of files. Once resolved, the second error disappeared, but not the first one when i want to use the store in patchState in an nx lib (not buildable)

[alcaidio]

The error occur in all my nx libs.

Argument of type '{ ...}>'.
  Types of property '[STATE_SOURCE]' are incompatible.
    Type 'Signal<{ ... }>': set, update, asReadonly, [ɵWRITABLE_SIGNAL]

[rainerhahnekamp]

Can you provide a snippet?

[alcaidio]

How can i provide you a snippet ?

[rainerhahnekamp]

That error message must come from some part of your code that you've written. Can you provide that or is it failing compile the SignalStore library?

[alcaidio]

Sorry for the late reply, here are two screenshots, I hope that's enough?

[rainerhahnekamp]

@brandonroberts will cae429a fix that? Looks that way.