Closed gclapham closed 6 months ago
I fixed the issue. The migrate command didn't rewrite all configs. I still had some pointing to @nrwl, which I edited manually.
if not to @nrwl, where should it point to? @nx ?
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
Invoking any nx command, eg
npx nx run my-app-name:serve:development
results inI created a fresh nx repo and copied the project files over to it – this runs but gives me separate issues with migrating Angular and not being in sync with GitHub.
Expected Behavior
It should run nx commands from the nx panel in VsCode and the terminal.
GitHub Repo
can't send for security reasons
Steps to Reproduce
Nx Report
Failure Logs
No response
Package Manager Version
yarn 1.22.21
Operating System
Additional Information
I am trying to migrate an old Nx project, Node 14.17.1 with @rewl/cli@12.2.11 to Node 18.19.1 nx@18.1.0.
I have run and rerun migrates on individual packages and eventually tried a blanket
npx nx migrate latest
I have repeatedly dumped the node_modules and yarn.lock and run and rerunnx reset
Still I get the Error
NX tasksRunner is not a function
on any nx command I try to run, from the VsCode console or command line.I created a fresh project and copied the app over – this does run nx commands, albeit with a myriad Errors due to the bumped version of Angular. Both projects are using nx 18.1.0.
Package.json for the failing project is below: