Replies: 1 comment 1 reply
-
We do have some external examples that we've encouraged people to use with |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After having spent a lot of time looking into ways of mitigating all the
degit
issues that are occurring increate-astro
, I have started to wonder if it is even a good idea to support using other examples than our own. This thought came to me after having checked out some othercreate-*
packages where I saw that almost none of them supported any other templates than their own ones.If you take a look at Vite's documentation about this, you can see that they only support their own examples, and then have instructions on how to do it with community templates. Next.js does almost the same, except that they don't tell you how you can use other templates as well.
I am suggesting that we should do the same thing with
create-astro
, and limit it only to the official examples/templates while still giving instructions about how to download other templates. This would first and foremost make us able to removedegit
and create our own downloading logic. Of course there are also a couple of ways to do that, we could either go the Vite way and make use offs
to just straight up copy the files, or we could go the Next.js way and download a tar of the code and extract it. There are many options, but I definitely think that it would be worth it in the long run instead of having to deal with all the issues that comes withdegit
.I am willing to make a PR that implements this, but it would need to be discussed a bit before that.
Beta Was this translation helpful? Give feedback.
All reactions