Closed jericopingul closed 2 years ago
The solution is that removing workspaces
in the root package.json and referencing by name @my-nx-npm/my-nx-plugin
in the project.json fixes it and fixes the node_module resolution. Thank you @AgentEnder
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
Referencing an executor's package name in the same workspace doesn't work
Expected Behavior
We should be able to reference like this in the same package
Not sure if this is a regression.
Steps to Reproduce
More details in the slack thread here: https://nrwlcommunity.slack.com/archives/CMFKWPU6Q/p1655840406201759?thread_ts=1655827506.379309&cid=CMFKWPU6Q
github source code : https://github.com/jericopingul/nx-npm/tree/main/packages
This issue may not be prioritized if details are not provided to help us reproduce the issue.
Failure Logs
Environment
Dev environment nx cloud command error: https://nx.app/runs/YrXuu40QXOR