[BUG] Prepare script not running

[tejohnso]

I've searched a number of issues related to prepare but could not find quite the same scenario.

Current Behavior:

npm install does not run prepare script and does not install devDependencies

Expected Behavior:

npm install should run prepare script and install devDependencies

Steps To Reproduce:

1. Create a private repo on github with a prepare script in the package.json file
2. npm init -y in a local test folder
3. npm install git+ssh://git@github.com:ghname/ghrepo#semver:^0.0.0
4. Observe prepare script is not run

Environment:

OS: Arch Linux
NPM: 7.6.3
NODE: 15.11.0

[ljharb]

Dev deps should only be installed when running npm install with no arguments.

[tejohnso]

If a package being installed through git contains a prepare script, its dependencies and devDependencies will be installed, and the prepare script will be run, before the package is packaged and installed

That's not what I understand from the documentation

Also, even if a step 3a npm install is added, it still doesn't work.

[ljharb]

ah, fair enough.

[nlf]

what is your prepare script doing? it's very likely it's running and we're just suppressing the output. one of the major changes in npm 7 is that we no longer display the results of lifecycle scripts at installation time in an attempt to reduce noise.

if, however, your prepare script is doing work like creating or modifying files and that modification isn't taking place, if you can give us a reproduction case with a real repo that would help a lot in addressing this for you.

[tejohnso]

It's running npm run build which runs some compilation tasks, so I know it isn't running because the compiled files aren't created.

This is only happening in a private repo. Should I create one for testing purposes and invite you?

[sxn]

Hi @nlf. I've encountered this bug as well, when using tarball dependencies. I've also created a repository to reproduce the issue: https://github.com/sxn/prepare-repro

[darcyclarke]

This needs a bit more investigation our end; Potentially this is intentional but prioritizing accordingly (seems like v6 was doing this)

[etn0m]

Any updates on this end? It'd be better to not have to downgrade to v6 for this feature.

[OmgImAlexis]

Confirmed this is 100% an issue #3800

This was also an issue in v6 #3800 (comment)