create-astro does not work

[ScriptRaccoon]

What version of astro are you using?

1.6.0

Are you using an SSR adapter? If so, which one?

None

What package manager are you using?

npm

What operating system are you using?

Windows 10 Pro for Workstations

Describe the Bug

When I run npm create astro@latest and follow the instructions, I get the following error and the installation fails:

D:\Development>npm create astro@latest

+—————+  Houston:
| ^ u ^  Let's build something awesome!
+—————+

 astro   v1.6.0 Launch sequence initiated.

? Where would you like to create your new project? » astro-example

√ Where would you like to create your new project? ... a

√ How would you like to setup your new project? » an empty project
          ■■▶ Copying project files...
npm ERR! code 1
npm ERR! path D:\Development
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c create-astro

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Martin\AppData\Local\npm-cache\_logs\2022-10-28T11_04_46_771Z-debug-0.log

2022-10-28T11_04_46_771Z-debug-0.log

It is also strange that, after answering the question about the location and press Enter, I need to press Enter again, it then takes the first letter of my answer only. It seems to ask the same question twice.

The same error happens when I use command line with administrator rights, Window's Powershell, and Git Bash.

Node version: v18.2.0
Git version: git version 2.38.1.windows.1

Sorry, I cannot add a minimal reproducible example here since the starter templates already have astro installed.

I can install astro manually as a depencency to a project and work with it. Only the installation wizard fails to work.

Link to Minimal Reproducible Example

sorry, left blank

Participation

• I am willing to submit a pull request for this issue.

[natemoo-re]

Hey @ScriptRaccoon I'd love to help narrow this down. I'm curious if the same command works for you when using an earlier version of Node, like node@16? That's my best guess at the moment.

[natemoo-re]

Since it seems like the prompts behavior is buggy, I thought you might be hitting a case where create-astro exits if a value isn't provided.

I opened #5240 to make these failures a bit more obvious, but I'm still not sure what could be causing the prompts issue.

[ScriptRaccoon]

Hey @ScriptRaccoon I'd love to help narrow this down. I'm curious if the same command works for you when using an earlier version of Node, like node@16? That's my best guess at the moment.

I can try this. How can I execute create-astro with another Node version (without uninstalling my current Node version)?

[natemoo-re]

If you're not using something like https://github.com/nvm-sh/nvm or https://volta.sh/ you would have to uninstall your current version and install the older one. No worries if that's too much.

[fullmetalbrackets]

Experiencing the same problem, but only in Windows PowerShell. It just gets stuck after "where would you like to create your project?"

Tried on Ubuntu, no problem there, prompts/dialog works fine and creates the project. Only seems to be an issue in Windows.

Node v.18.12.0 on both machines.

[vaakian]

the same problem on my machine with node v18.1.0,
was resolved to downgrade to node v16.

[ScriptRaccoon]

The tool works on my machine when Node 16.0.0 is installed. But it still asks the question where to create the project (i.e. the folder) twice and then takes the first letter of the first answer combined with the second answer. So when you just press Enter another time (what I first did), you only get one letter.

? Where would you like to create your new project? » astro-example
test
√ Where would you like to create your new project? ... atest

[frerova91]

I had the same problem in linux. i fix it updating node to the last lts version. it seems that in the process of testing pnpm with astro i had corepack enable, then the error appear. i was usign node 18.0.0 that use pnpm 6.0 and the last version is 7.14 at this moment that caused that neither npm or pnpm to be able complete create astro@latest

[viniciusflv]

I'am also having an issue on windows 10.

node v16.18.0
npm v8.19.2

npm create astro@latest
npm WARN exec The following package was not found and will be installed: [email protected]

+—————+  Houston:
| ^ u ^  Let's create a new project!
+—————+

 astro   v1.6.1 Launch sequence initiated.

? Where would you like to create your new project? » ./laughable-luminosityfile:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:1
        process.stdin.setRawMode(false);
                      ^

TypeError: process.stdin.setRawMode is not a function
    at done (file:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:14:23)
    at say (file:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:81:5)
    at async main (file:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/create-astro/dist/index.js:78:5)


``` npm create astro
npm WARN exec The following package was not found and will be installed: [email protected]

+—————+  Houston:
| ^ u ^  Let's create a new project!
+—————+

 astro   v1.6.1 Launch sequence initiated.

? Where would you like to create your new project? » ./laughable-luminosityfile:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:1
        process.stdin.setRawMode(false);
                      ^

TypeError: process.stdin.setRawMode is not a function
    at done (file:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:14:23)
    at say (file:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:81:5)
    at async main (file:///C:/Users/<username>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/create-astro/dist/index.js:78:5)

[dtinth]

The process.stdin.setRawMode error happens when create-astro is run inside a shell script with non-tty stdin.

Example bash:

yarn create astro fresh-app --template basics --install --git=false --typescript=strict < /dev/null

[mrienstra]

Does this issue occur with prior versions of create-astro? Instead of e.g.
pnpm create astro@latest, try:

pnpm create [email protected]

Quick reference:

After #5240	[email protected] (latest)
Before #5240, after #5088	[email protected]
Before #5088, after #4810	[email protected]
Before #4810	[email protected]

[dtinth]

@mrienstra It started occurring in v1.2.0.

I'm maintaining Fresh App Factory, a project that runs generator scripts every day and publish the generated project as GitHub template repositories (here's a fresh-astro-project). The Astro project generation script stopped working 6 days ago.

• The logs for last working build before it broke indicates v1.1.0.
• The logs for the first broken build indicates v1.2.0.

[mrienstra]

@dtinth, thanks! primer/brand#113 is saying the same thing (v1.1 working, v1.2 broken). I forgot to mention that before.

I was asking in case there are multiple issues being discussed here.

[jigz]

issue is present on node v16, just so you know
windows 10, node v16.14.0, npm v8.2.0

[mrienstra]

1. It seems like there are several distinct issues being discussed here:
   A) unspecific error while copying project files
   B) buggy prompts (can occur with (A))
   C) unresponsive (could be a variant of (B))
   D) setRawMode error
2. Tempting to temporarily revert [Create Astro] Improved prompts, template handling, Houston #5088 and release a new version of create-astro, to keep the "first time" user experience on Windows painless.

[natemoo-re]

OK, quite a few issues happening here...

1A. I've had a hard time tracking down what could be going on here. If anyone can nail down a reproduction that would be very helpful.

1B + 1C. Seems like this might have something to do with setRawMode being called before the prompt runs? There are some issues about Windows bugginess reported on prompts, but they don't seem particularly relevant.

If anyone who is experiencing bugginess on Windows could try running the command again with --skip-houston that would rule out that the opening animation is causing any problems.

1D. setRawMode issue should be fixed by withastro/cli-kit@1c61aa5

[viniciusflv]

@natemoo-re, about the 1D scenario with the --skip-houston flag.
It works, but in the end fails again. Maybe because houston showed up again.

But as you said:

1D. setRawMode issue should be fixed by withastro/cli-kit@1c61aa5

Just wanted to give feedback.

...
√ How would you like to setup TypeScript? » Strictest
√ TypeScript settings applied!

  next   Liftoff confirmed. Explore your project!

         Enter your project directory using cd ./shaky-sphere
         Run npm run dev to start the dev server. CTRL+C to stop.
         Add frameworks like react or tailwind using astro add.

         Stuck? Join us at https://astro.build/chat

+—————+  Houston:
| ^ u ^  Good luck out there, astronaut!
+—————+
file:///C:/Users/<user>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:14
        process.stdin.setRawMode(false);
                      ^

TypeError: process.stdin.setRawMode is not a function
    at done (file:///C:/Users/<user>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:14:23)
    at say (file:///C:/Users/<user>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/@astrojs/cli-kit/dist/messages/index.js:81:5)
    at async main (file:///C:/Users/<user>/scoop/persist/nodejs-lts/cache/_npx/57e9a3bcc0672894/node_modules/create-astro/dist/index.js:297:3)

[natemoo-re]

OK a few fixes landed in #5319 but I'm still stuck without reproductions on a few of the other ones. Luckily I have a Windows machine on the way, so hopefully I can track these down myself once that's here.

[ScriptRaccoon]

Great! With v1.6.7 the primary error does not appear anymore (on my PC, at least). Only the name question is still buggy:

npm create astro@latest test-astro

works as expected. However, as before,

npm create astro@latest

asks me for the project name twice concatenates the first letter of the first answer with the full second answer.

+—————+  Houston:
| ^ u ^  I'll be your assistant today.
+—————+

 astro   v1.6.7 Launch sequence initiated.

? Where would you like to create your new project? » my-astro-project
it-asks-again
√ Where would you like to create your new project? ... mit-asks-again

[natemoo-re]

Interesting, thanks for the update! That should help me narrow things down.

[backflip]

@natemoo-re, possibly related: Running npm create astro@latest on Node 18.12.1 does not allow me to delete or overwrite the auto-generated name in the Where would you like to create your new project? prompt. Instead, it will concatenate my input with the default value and then render it a second time after pressing enter:

UPDATE: This only happens when pressing delete initially. When I immediately start typing, the default value is replaced.

[nathobson]

I was also getting the same error as the original issue reported but on MacOS Ventura 13.0 and Node v18.2.0.

The error is pretty much the same as the original post:

✔ How would you like to setup your new project? › a few best practices (recommended)
          ■■▶ Copying project files...
npm ERR! code 1
npm ERR! path /Users/nat/web
npm ERR! command failed
npm ERR! command sh -c create-astro

This was fixed using NVM to use Node 16 to run the installer.

[TheNormandyProject]

@natemoo-re It always fails on this command sh -c create-astro, even when in sudo mode. I've tried on Windows and your new patch works just fine. Just not on my main development machine (macOs Monterey arm64)

[YUUSUKE18]

@natemoo-re I tried your post, but I met the same error.

npm ERR! command failed
npm ERR! command sh -c create-astro

Here is my env.

Node v18.1.0 (I use nodenv)
Mac M1
Mac OS Ventura

Thank you!

[natemoo-re]

Any chance running the command as npx create-astro@next--refactor works?

Alternatively, upgrading npm to the latest version for v18 or v19 and clearing your cache?

If everything continues to fail, a full screen recording would be the most helpful way to debug this.

[YUUSUKE18]

@natemoo-re

Hi, I tried all of them in this post, but not work well.
Here is screen shot.

It seems to work well, but astro directory was not created.
Here is my env again.

Node 18.8.0 (I use nodenv)
npm 8.8.0
Mac M1
Mac OS Ventura

[natemoo-re]

This was automatically closed by my merge. Reopening.

[natemoo-re]

Do both of you have git installed? I wonder if our dependendency giget is failing silently here?

Can you try to run the following command?

npx giget@latest gh:withastro/astro/examples/basics my-project

[YUUSUKE18]

@natemoo-re

I tried, but the error is keeping...

Here is my error and git version.

[TheNormandyProject]

Using X-code git 2.39.1

[mrienstra]

Might be time to close this and open new issues, as create-astro has changed a fair bit in the 3+ months since this issue was opened. There may not be a lot of overlap between prior issues and new issues, though of course there could be a common root in some cases.

I just tried pnpm create astro@next--refactor while my network was heavily throttled, and it was stuck on "Template copying..." for quite awhile. Part way through, I saw that the directory was created, but it was empty. Hitting Ctrl-C caused lines above "Template copying..." to disappear one by one, very odd! Eventually it moved forward to the next step, and ended up finishing fine, despite my attempts to cancel it. I filed a new issue for the inability to cancel during copying: #6165

I then ran nvm install 18.14.0, and before running corepack enable (& corepack prepare pnpm@latest --activate), I inadvertently ran create-astro with pnpm 6.14.3 (ancient, Aug 23, 2021, from homebrew) & found a funny bug, probably not worth addressing, pnpm create astro@next--refactor resulted in
 ERROR  No package.json (or package.yaml, or package.json5) was found in "/Users/foo/bar".

Also ran across this weird bug: #6166

... Otherwise working well for me!

[natemoo-re]

Very interesting, thanks for investigating @mrienstra!

I definitely agree with closing this issue since it's been running for quite a long time and we're discussing entirely different problems at this point.

Since this command is failing for @YUUSUKE18 and @TheNormandyProject...

npx giget@latest gh:withastro/astro/examples/basics my-project

That leads me to believe that the underlying issue with the Copying template... step is upstream with giget. I would highly recommend opening an issue there and sharing as much information as you can.

I unfortunately don't think there's anything we're able to do on our end, short of switching to another project downloader or building our own, which we'd like to avoid.

Continuing the convo on #6165 and #6166

[ScriptRaccoon]

Closing is OK for me, since the errors from the first post do not happen anymore (Windows 10, Node v18.12.0).

[YUUSUKE18]

@natemoo-re

Thank your for your support.
I make sense closed this topic.

I checked this problem.
Here is additional information

• Mac Ventura does not work for all of commands in astro.
• Mac Monterey works well for all of commands in astro.

My co-worker env is Mac Monterey. That's why he tried commands in this topic.
I imagined Mac OS Ventura is a problem for this problem.
But not sure why it is problem.

[mrienstra]

@YUUSUKE18 & @TheNormandyProject, the error you both get when running npx giget@latest gh:withastro/astro/examples/basics my-project looks to be coming from undici, via giget --> node-fetch-native --> node --> undici. I'd love to help support opening a giget issue as @natemoo-re suggested. Unfortunately I haven't been able to reproduce this issue myself, not even with an older node v18 release (v18.1.0).

	@YUUSUKE18 (error)	@TheNormandyProject (error)	@mrienstra (working)	@YUUSUKE18's co-worker (working)
macOS	13.x (Ventura)	12.6.3 (Monterey)	12.6.3	12.x
CPU/GPU (SoC)	M1	M1 Max	M1	?
node	v18.1.0, v18.8.0	v18.2.0	v18.1.0, v18.14.0	?
node version manager	nodenv	nvm	nvm	?
git	2.37.1 (Xcode)	2.39.1 (Xcode)	2.39.1, (Homebrew)	?

Latest macOS Monterey is 12.6.3, latest Ventura is 13.2, latest node v18 is v18.14.0, latest git is 2.39.1.

PS: well off topic, but @YUUSUKE18, according to this, you may want to use a newer version of git, either by updating Xcode, or installing some other way, e.g, Homebrew, which is the first option listed at https://git-scm.com/download/mac (though the order may not be particularly meaningful, take that with a grain of salt).

edit: added to table as per comment below

[TheNormandyProject]

@YUUSUKE18 & @TheNormandyProject, the error you both get when running npx giget@latest gh:withastro/astro/examples/basics my-project looks to be coming from undici, via giget --> node-fetch-native --> node --> undici. I'd love to help support opening a giget issue as @natemoo-re suggested. Unfortunately I haven't been able to reproduce this issue myself, not even with an older node v18 release (v18.1.0).

@YUUSUKE18 (error) @TheNormandyProject (error) @mrienstra (working) @YUUSUKE18's co-worker (working)
macOS 13.x (Ventura) 12.x (Monterey) 12.6.3 12.x
CPU/GPU (SoC) M1 M1 Max M1 ?
node v18.1.0, v18.8.0 v18.2.0 v18.1.0, v18.14.0 ?
node version manager nodenv ? nvm ?
git 2.37.1 (Xcode) 2.39.1 (Xcode) 2.39.1, (Homebrew) ?
Latest macOS Monterey is 12.6.3, latest Ventura is 13.2, latest node v18 is v18.14.0, latest git is 2.39.1.

PS: well off topic, but @YUUSUKE18, according to this, you may want to use a newer version of git, either by updating Xcode, or installing some other way, e.g, Homebrew, which is the first option listed at https://git-scm.com/download/mac (though the order may not be particularly meaningful, take that with a grain of salt).

I use nvm for my Node Version Manager :)
And I'm on Monterey Latest

[pontakornth]

I worked around this by using Node 16.16.0 for project creation and switch back to Node 18.2.0.

[mrienstra]

@pontakornth, can you provide a little more detail? How did it fail on Node 18.2.0? If you haven't already, can you try running the following (as per this comment) using Node 18.2.0 to see if it fails as well?

npx giget@latest gh:withastro/astro/examples/basics my-project

[grande-zeno]

Another work around would be to install astro manually. Works with the latest version of node.

[cbolson]

Another work around would be to install astro manually. Works with the latest version of node.

I have been having exactly the same issues as outlined in this thread. Having tried pretty much everything suggested here, I finally got to the end of the thread just as you suggested doing a manual install. I have tried it, and I have finally been able to set up and run dev. Thanks for the suggestion @tinus-bot

Update - I just tried a fresh installation to see if anything had changed. I got the same error error command sh -c create-astro.
I decided to uninstall the package via npm uninstall astro and the strangest thing happened - rather than uninstalling Astro it actually finished the installation, and it is now working with no errors.
My understanding of npm is very limited, but I did not expect that!.

[ezeamin]

I add to the discussion. I'm having the same problem when going through the 2nd step:

My env is:
pnpm 7.29.1
node 18.2.0 (tried it with npm but got the same result)
npm 9.5.0
Windows 11

[huaji1992]

╭─────╮ Houston:
│ ◠ ◡ ◠ Let's build something awesome!
╰─────╯

astro v2.1.7 Launch sequence initiated.

dir Where should we create your new project?
./astro_play

tmpl How would you like to start your new project?
Include sample files
██████ Template copying...
zlib: unexpected end of file
 ERROR  Command failed with exit code 1: create-astro

pnpm: Command failed with exit code 1: create-astro
at makeError (/Users/nobug/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/pnpm/dist/pnpm.cjs:24230:17)
at handlePromise (/Users/nobug/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/pnpm/dist/pnpm.cjs:24801:33)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.handler (/Users/nobug/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/pnpm/dist/pnpm.cjs:215154:7)
at async /Users/nobug/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/pnpm/dist/pnpm.cjs:222970:21
at async main (/Users/nobug/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/pnpm/dist/pnpm.cjs:222937:34)
at async runPnpm (/Users/nobug/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/pnpm/dist/pnpm.cjs:223192:5)
at async /Users/nobug/Library/pnpm/global/5/.pnpm/[email protected]/node_modules/pnpm/dist/pnpm.cjs:223184:7
(base) ➜ ~

[HBFLEX]

the install finally worked with npm create astro@next--refactor command. Thank you

[ericdain]

Thanks all for taking the time to post here! I've just been playing with create astro@latest (v2.5.0) and for me it was nodejs v18 that kept resulting in failure at the tmpl step.

• nodejs 18.0.0: FAILED
• nodejs 16.9.1: SUCCESS
• nodejs 20.2.0: SUCCESS

[StefanoTesla]

same problem with Node.js v18.16.1 and [email protected]

[brainstem-sys]

Hey @natemoo-re 👇🏻

DEV env:
Operative System: Windows 10 22H2 Pro N x64 build 19045
Node Manager: FNM v1.35.1
NodeJS: 18.18.0
NPM: 10.1.0
PNPM: 8.7.6
Terminal: PWSH v7.3.7 or Powershell v5.1 (Windows default terminal)

To create a new Astro project using the automated CLI I used the commands:
NPM i ASTRO NPM CREATE ASTRO@LATEST NPM CREATE ASTRO@LATEST --SKIP-HOUSTON NPM CREATE ASTRO@NEXT--REFACTOR NPX CREATE-ASTRO@NEXT--REFACTOR NPM INSTALL --SAVE-DEV ASTRO

...and when they do not throw privilege error they simply fail by displaying the ENOTEMPTY code. I cleaned cache before and after the execution of each, tested in completely empty directories/partitions, updated, reinstalled Node and P/NPM via FNM without any results. Attached images on the execution of the different commands and log.

PS: with this same dev env I have created projects of React, Tailwind + daisyUI, Vue on Node without any problem, however Astro still resists.

[mahindev-ai]

I have the same issues with next env on windows 11:
node v20.11.0
npm 10.3.0
git version 2.43.0.windows.1

The only solution that I found it was install manually astro as @honkingeagle said

Another work around would be to install astro manually. Works with the latest version of node.

[brainstem-sys]

@mahindev-ai fixed by simply installing NVM for Windows