Closed stipsan closed 2 years ago
/[[...slug]] |
---|
(view full size) |
And 1 other route:
Commit 29f4df39c66e0dd8a3bca88aed2995f39d2b98a8 (https://template-nextjs-landing-pages-eawihiu7v.sanity.build).
Hi, noticed the same on this starter project. Slightly frustrating as this is pretty much the single project starter I need to get Sanity up and running for our use case.
You can't test it with sanity/create before merging
But you can use this button until then:
When I tried running this earlier today this is what I saw:
logs
![image](https://user-images.githubusercontent.com/81981/187043013-1bcbf583-661c-4506-ada0-1e1e3b16eca1.png)At first it was tempting to just see if all the trouble was just a missing
--legacy-peer-deps
somewhere. But after I wasted a ton of time earlier this week trying to migrate a gatsby starter that way and ultimately failing I instead moved this starter to the same setup as I did for https://github.com/sanity-io/sanity-template-nextjs-blog-commentsI would've loved to have time to give the docs and readme some love. But for now priority 1 was to get it functional and automated. More automation makes it more realistic we'll be able to keep it up to date.
Quick list over changes that happened to https://github.com/sanity-io/sanity-template-nextjs-blog-comments earlier today, and what's proposed to https://github.com/sanity-io/sanity-template-nextjs-landing-pages in this PR:
NPM_TOKEN
.npx prettier --write .
before you push your changes a friendly bot will fix it for you instead of giving your PR a failed check blocking you from merging.