You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while teaching a student to build in react, we consulted the react docs.
this student, using Windows, installed node, confirmed that npm existed, made a github repo, and navigated into the new repo and ran the command literal provided in the React docs: npx create-next-app@latest
This errored unexpectedly, complaining that there was no npm folder in their /Roaming/ folder
the solution was simply to make an npm folder inside Roaming and everything else worked.
Proposal
I currently believe this should be fixed npx-side, but I could be mistaken
if the npx program is proceeding into create-next-app, then we should make sure to create the folder if it doesn't exist ourselves
if the next/vercel team agrees it's an npx-side issue feel free to close and a +1 on the issue below would be helpful! npm/cli#7205
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
npx create-next-app@latest
to work out of the box as suggested in the React docsnpm folder does not exist
error on Windows by ensuringnpm
exists underRoaming
if neededrelated
Non-Goals
Background
related on npx side: npm/cli#7205
while teaching a student to build in react, we consulted the react docs.
this student, using Windows, installed node, confirmed that npm existed, made a github repo, and navigated into the new repo and ran the command literal provided in the React docs:
npx create-next-app@latest
This errored unexpectedly, complaining that there was no
npm
folder in their /Roaming/ folderthe solution was simply to make an npm folder inside Roaming and everything else worked.
Proposal
I currently believe this should be fixed npx-side, but I could be mistaken
if the npx program is proceeding into create-next-app, then we should make sure to create the folder if it doesn't exist ourselves
if the next/vercel team agrees it's an npx-side issue feel free to close and a +1 on the issue below would be helpful!
npm/cli#7205
Beta Was this translation helpful? Give feedback.
All reactions