Nx extension does not work with latest pnpm and zsh
See original GitHub issueCurrent Behavior
nx console extension does not work when used with
- pnpm
- nx 13.8.0
Expected Behavior
Should work ❤️
Steps to Reproduce
- Install zsh
- install nvm
- install pnpm globally
- install the nxconsole extension
- try running any task
- pnpm is added into the path variables, in my case,
❯ which pnpm
/Users/n0s00jx/.nvm/versions/node/v16.6.2/bin/pnpm
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (2 by maintainers)
Top Results From Across the Web
angularjs - zsh: command not found: nx - Stack Overflow
I am trying to create a library in Angular using nx g @nrwl/angular:lib shared but it keep giving me error zsh: command not...
Read more >Pnpm and Nx monorepo. Part 3 | Javier Brea
Now we are going to see how to create a continous integration workflow for the Nx and Pnpm monorepo using Github actions.
Read more >Intro to Nx
Intro to Nx. Nx is a smart, fast and extensible build system with first class monorepo support and powerful integrations.
Read more >Setup a Monorepo with PNPM workspaces and speed it up ...
In this article we're going to have a deep dive into setting up a new monorepo using PNPM workspaces that hosts a Remix...
Read more >lint-staged - npm
Latest version: 13.1.0, last published: 21 days ago. ... Run linters against staged git files and don't let slip into your code base!...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
this works ! Thanks a lot
Try changing the settings for the terminal like mentioned here: https://github.com/nrwl/nx-console/issues/1207#issuecomment-1025007577
Specifically look into the
terminal.integrated.profiles
setting on the VSCode side