feat(gatsby-cli): enable set packagemanager

[laurieontech]

CLI should default to npm and remove the selection option.

We'll then create a separate CLI option that allows a user to change their package manager.

For long term flexibility this command is config and can also be used to report telemetry.

[ch7523]

[gatsby-cloud]

Gatsby Cloud Build Report

gatsby

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 23m

[wardpeet]

Looking good! I'm not sure why we want to remove the package-lock files

[gillkyle]

Just tested this locally and read through what's going on. Even though I don't know all the implications of how the sausage is made, the sausage comes out looking good to me 😄 :

Successful

Error

[pieh]

CLI should default to npm and remove the selection option.

I'm not sure if I understand "remove the selection option" here. Does it mean it should "forget" package manager setting that was selected before (through prompt thingie)? If so I can't see how this happens right now.

[laurieontech]

@pieh poor phrasing, it means that we are removing the prompt code and doing it differently. It will listen to your existing selection if you have one.

[wardpeet]

Looks good, thank you @laurieontech

[wardpeet]

Looks good, thank you @laurieontech

[wardpeet]

Successfully published:

• [email protected]

[arcanis]

This breaks installs using Yarn 2 - npm isn't compatible with it (cf the following run). Can you at least detect which package manager is currently used (by looking at the value of $npm_config_user_agent)?

[wardpeet]

@arcanis Thanks for pointing that out and TIL about $npm_config_user_agent. How do you use it with yarn 2?

[arcanis]

It's set in the environment (here). If you see yarn/ in it, I'd suggest to default to Yarn instead of npm.