Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create-next-app not working #35599

Closed
1 task done
ghost opened this issue Mar 25, 2022 · 5 comments · Fixed by #35608
Closed
1 task done

create-next-app not working #35599

ghost opened this issue Mar 25, 2022 · 5 comments · Fixed by #35608
Labels
bug Issue was opened via the bug report template.

Comments

@ghost
Copy link

ghost commented Mar 25, 2022

Verify canary release

  • I verified that the issue exists in Next.js canary release

Provide environment information

node and npm version
image

operating system windows 10

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

I try creating a next project with npx but in windows console this error:
"'yarn' is not recognized as an internal or external command, operable program or batch file."

Expected Behavior

I'll intent build a nextjs project

To Reproduce

with @latest

  • image

without @latest

  • image
@ghost ghost added the bug Issue was opened via the bug report template. label Mar 25, 2022
@antonbobrov
Copy link

I've struggled the same issue.
This would help:
npx create-next-app@latest --ts --use-npm

@ghost
Copy link
Author

ghost commented Mar 25, 2022

I've struggled the same issue. This would help: npx create-next-app@latest --ts --use-npm

thanks I love you

@ghost
Copy link
Author

ghost commented Mar 25, 2022

npx create-next-app@latest --ts --use-npm

@ghost ghost closed this as completed Mar 25, 2022
kodiakhq bot pushed a commit that referenced this issue Mar 26, 2022
This fixes our package manager detection which was changed slightly in #34947 for `pnpm` support to ensure the default case still attempts detecting the available package manager if no preference is specified in the command args. This also adds a test case to ensure the install succeeds when we fail to detect a valid `yarn` binary and no preference is set via the `npm_config_user_agent` env variable. 

## Bug

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

Fixes: #35607
Fixes: #35599
@ijjk
Copy link
Member

ijjk commented Mar 28, 2022

Hi, this has been fixed in the latest version of Next.js v12.1.2 please give it a try! Note: this may require running with @latest e.g. npx create-next-app@latest.

@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 28, 2022
LuighiV pushed a commit to openpolitica/create-openpolitica-nextjs-app that referenced this issue Aug 24, 2022
This fixes our package manager detection which was changed slightly in vercel/next.js#34947 for `pnpm` support to ensure the default case still attempts detecting the available package manager if no preference is specified in the command args. This also adds a test case to ensure the install succeeds when we fail to detect a valid `yarn` binary and no preference is set via the `npm_config_user_agent` env variable. 

## Bug

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

Fixes: vercel/next.js#35607
Fixes: vercel/next.js#35599
pavleadev added a commit to pavleadev/next.js that referenced this issue Mar 29, 2023
This fixes our package manager detection which was changed slightly in vercel/next.js#34947 for `pnpm` support to ensure the default case still attempts detecting the available package manager if no preference is specified in the command args. This also adds a test case to ensure the install succeeds when we fail to detect a valid `yarn` binary and no preference is set via the `npm_config_user_agent` env variable. 

## Bug

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

Fixes: vercel/next.js#35607
Fixes: vercel/next.js#35599
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants