-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Fix misc create-astro issues #4075
Conversation
🦋 Changeset detectedLatest commit: 4b6ef87 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -246,7 +312,7 @@ export async function main() { | |||
)} to your project using ${bold(cyan('astro add'))}` | |||
); | |||
await logAndWait(''); | |||
await logAndWait(`Stuck? Come join us at ${bold(cyan('https://astro.build/chat'))}`, 1000); | |||
await logAndWait(`Stuck? Come join us at ${bold(cyan('https://astro.build/chat'))}`, 750); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fred talked about a sleep being too long in create-astro
, however he didn't specify which one. I can only assume it's this one, which did feel long
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, just needs a changeset 👍
Changes
Fixed some small misc issues with
create-astro
. Polishing, essentially.Fix #3825
Fix #3824 👻😨
Fix #3826
Didn't tackle #3561 in this because I couldn't reproduce it? The peer issue part is unrelated to
create-astro
and the main part (pnpm 6
not detected) worked for me, not sureTesting
I tried testing some parts of this, but I kept getting weird mocha errors? We don't test much of
create-astro
at the moment, so I figured it was fine to not test this for nowDocs
Since this is mostly error handling being done, it doesn't touch the current documentation