npm init next-app creates a project that uses yarn

[pjaws]

Bug report

Describe the bug

Running npm init next-app creates a new Next.js project that uses Yarn, rather than npm. Given, the fact that I'm using npm to create the project, and the docs offer two options for getting started, one with npm and one with Yarn, this is completely unexpected behavior.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Read getting started docs
2. Choose the npm option
3. Run npm init next-app
4. Get a project that uses Yarn

Expected behavior

It should create a project that uses npm for package management.

Here ya go, Tim!

[timneutkens]

Already answered as per #10642 (comment)

This is expected behavior as you have yarn installed.

[pjaws]

How could you possibly think that running npm init would create a project with yarn? This is absolutely not expected behavior for the end user. I've noticed this happening in many Next.is issues. You come in and make some short comment then close the ticket without any further investigation or conversation. This is at the very least a documentation issue. It is not obvious at all that when you offer an npm option and a yarn option, that choosing the npm option will lead to the project being created with yarn. Whether or not I have yarn installed is completely irrelevant.

…

On Sun, Feb 23, 2020 at 1:38 PM Tim Neutkens ***@***.***> wrote: Closed #10647 <#10647>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10647>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMVRRISPQ52LIOT6VDFMMY3RELUFDANCNFSM4KZ36YKA> .

[timneutkens]

@lfades let's update the docs to just mention npx.

[timneutkens]

How could you possibly think that running npm init would create a project
with yarn?

I'm saying it's expected behavior and implemented this way by design, here's the yarn check:
https://github.com/zeit/next.js/blob/canary/packages/create-next-app/index.ts#L101

[pjaws]

Sorry, I guess we were misunderstanding each other, and that’s my fault. I meant unexpected behavior from the user’s point of view. I should have mentioned from the start that I felt this was a documentation issue, not a code issue, though I do still feel it’s odd DX. Anyway, the problem can definitely be solved by a short line in the docs. I was going to add a PR myself, but I wasn’t sure how you all would want to phrase it, or which method was preferred (—use-npm or npx).

…

On Mon, Feb 24, 2020 at 8:54 AM Tim Neutkens ***@***.***> wrote: How could you possibly think that running npm init would create a project with yarn? I'm saying it's expected behavior and implemented this way by design, here's the yarn check: https://github.com/zeit/next.js/blob/canary/packages/create-next-app/index.ts#L101 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10647>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMVRRITSDCF2CH3E7NL252TREP3VDANCNFSM4KZ36YKA> .

[nkovacic]

I also agree with @pjaws. Even if we have have yarn installed, create-next-app should have a switch to use npm instead of yarn if its detected.

[Janpot]

FYI: Both npm and yarn should set an environment variable npm_execpath. Maybe that can be checked before the installation check to pick the right package manager? (I know it works on run, I'm not sure about init)

[timneutkens]

@tsriram did some investigation into how to detect npm here: #11628 (comment)

Happy to take in a PR as mentioned in that issue 👍

[tsriram]

This should be fixed in #11683. I guess this issue can be closed once the new version is published.

[onomated]

@tsriram is there anyway to fix this in existing codebases?

[vschoener]

Just run into the same issue today and was surprised next install by using yarn instead of npm.

Doc says:

npm init next-app
# or
yarn create next-app

So can you explain (or fix the documentation) because I'm really lost.

[mbrookson]

Anyone who comes here, I don't think it's well documented but I found you can install with npm using the --use-npm flag.

e.g.

npx create-next-app my-app --use-npm

# or 

npm init next-app my-app --use-npm

Hope this helps 🙂

[Timer]

FYI running npm init with npm v7 will no longer use Yarn.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.