-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Maintain a template repo #3422
Comments
Wouldn't it make more sense, if it would be run every time, new version of kit or create-svelte is deployed to npm? So there is not "unreleased" version of it in node.new / stackblitz ? |
Good point, it probably belongs in the release workflow (https://github.com/sveltejs/kit/blob/master/.github/workflows/release.yml), or the |
Should this be closed now that https://github.com/sveltejs/kit-template-default exists or is there more to do? |
Well, it's still private. We'd probably want to make it public, maybe mark it as a template repo in GitHub (although people should probably just use the CLI), and disable issues or otherwise limit contributions and update the repo description there so that stuff gets opened over here instead. |
we can close this now — https://github.com/sveltejs/kit-template-default is public, and powers https://sveltekit.new |
Describe the problem
If you go to https://node.new/sveltekit, it will create an out of date project. That's because we haven't supplied a template repo, so it's using a snapshot.
Describe the proposed solution
If we had a programmatic interface to
create-svelte
(#3421), then we could create a GitHub action that kept such a template repo up to date. This action would run on every commit tomaster
(and dryrun on all other commits?)Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response
The text was updated successfully, but these errors were encountered: