James Henry

@610 I'm sorry to hear about your Nx experience at that time, **I'm pleased to say that is indeed out of date in very significant ways.** Nx's TypeScript setup is...

@610 Ha no worries at all, I was subscribed to this thread already because of interest in the underlying topic, so I was able to see your response. We are...

I'm strongly thinking we will want to have a `prefer-signals` rule very soon, and having `prefer-signals` and `prefer-signal-readonly` is maybe a little clunky... It feels like `readonly` is pretty objectively...

I'm going to merge this into #2109 and apply some tweaks, many thanks again!

@reduckted I wasn't fully happy with the scope of the arbitrary typesToReplace and the implementation only considered things being instantiated with `new` which made sense for BehaviorSubject, but not the...

We can revisit preferring signals over arbitrary things in a dedicated follow up

**Background:** Peer dependencies in lerna have an extensive history of discussion: https://github.com/lerna/lerna/issues/1018 https://github.com/lerna/lerna/issues/3671 https://github.com/lerna/lerna/issues/2402 https://github.com/lerna/lerna/issues/955 Based on that past (that we inherited) any changes in this area are highly controversial....

Thank you for the comprehensive write up @stemcstudio @geometryzen (two accounts on one PR 😅 ?) I am happy to proceed with this as you have stated, with it's scope...

I pulled in the latest main just to give you the initial CI feedback ahead of further changes

I have updated the PR title to match the conventions needed for merge (and preemptively added workspace support in there)