nlf

hi there folks, linked above is a pull request that addresses this problem. it was unfortunately not as simple to fix as we had hoped. the reason for the strange...

this is a proposed fix, not a concrete solution. the problem as it stands is that we either place a node or we do not. if we do not place...

so a user is expected to know about an optional peer but not about an optional prod dependency? that doesn't really make sense to me. i can concede that the...

i think there's two separate issues here. 1. `npm install` allows changes to happen to your lock file, this differs from `yarn install` and can be a source of confusion....

@robations can you try replicating this problem on the latest version of `npm`? (ie. `npm i -g npm`) i tried it there myself and see your expected results. if you're...

if your `script-shell` setting is still `cmd` (which is the default) then this problem makes some sense, you might try something like `npm config set script-shell pwsh --location=user` and then...

it doesn't always use `cmd` it uses it _by default_. you are always free to tell npm to run under whatever shell you want it to. in addition to that,...

i don't _think_ that will be related to your issue here. i'll be looking into this one soon, though

unfortunately this isn't quite the right approach here, this changed behavior means that we'll always try to install an optional dependency, even if we're asked specifically not to. what we'll...

> > this changed behavior means that we'll always try to install an optional dependency, even if we're asked specifically not to. > > That's the right behavior, right? if...