sst: `sst init` errors in fresh directory
Discussion on Discord https://discord.com/channels/983865673656705025/1177071497974648952/1220196175165132881.
Trying to initialize an sst project in a completely new directory. Did the following.
mkdir sst-ion-testcd sst-ion-testpnpm initsst init
sst init when run with verbose just gives the following.
From SyncLinear.com | ION-216
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 19 (9 by maintainers)
I was able to track down the issue with my init after running with the newly provided details in --verbose. Init script was failing on bun install. I found this issue https://github.com/oven-sh/bun/issues/4988 it suggested that bun is having issues with ipv6. After disabling ipv6 init/bun works as expected. Maybe don’t use bun or get bun to fix the upstream bugs.
@thdxr I am still having some issues, here is what I did:
Steps
sst-curl -fsSL https://ion.sst.dev/install | bash(v0.0.193)npx create-next-app@latest ion-nextjs --typescript --tailwind --eslintcd ion-nextjssst-AWS_PROFILE="personal" sst init --verboseOutput