Adam Wootton

Just wanted to bring this up again because I'm doing another re-evaluation of how to version my packages with Nx. Currently using Lerna with a sketchy glue script that feeds...

Also just ran into this, in our case we were using a ref to store a reference to an instance of our SDK client which was being created in a...

That sounds good :) . It would be great if the package that is having its "unused status" ignored could still be checked for correct version matching against the root...

@meeroslav while these changes are being made I also think you should consider again the role that "externals" play in the linting rule's ability to provide safety. See my comment...

As I commented on the linked issue, I think there's a logical flaw in Nx trying to determine the type of package based on the `tsconfig` module setting. That seems...

I think it helps to remedy the issue once you know that's what the issue is, it's just that finding that out is usually really painful. It would be much...

Ran into this as well, it's a big pitfall during migration since it's not mentioned in the migration guide, and is definitely an unexpected side-effect of having that setting. I...

same issue trying to upgrade from nx 14 to nx 16, using yarn 3.6: ``` > NX Report complete - copy this into the issue template Node : 18.16.0 OS...

Hi @mandarini ! Sorry, I made a mistake in the repro steps. After renaming the target, I was correctly calling the newly-named target, eg. `nx nodejs` The problem appeared when...

I opened a PR against your repo that adds a reproduction of the issue: https://github.com/mandarini/tsc-target-name/pull/1