`create-svelte` output is missing `.gitignore`
See original GitHub issueDescribe the bug
create-svelte
output is missing .gitignore
To Reproduce
npm init svelte@next
Expected behavior
.gitignore
is included in the default template
Severity Oops.
Additional context Probably got missed by accident when we re-wrote the template to generate the JS version from the single TS version.
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
What's new in Svelte: June 2021
Update your .gitignore accordingly; trailingSlash: 'never' | 'always' | 'ignore' is now available in the config. This should make it easier ...
Read more >Getting started with Svelte - Learn web development | MDN
gitignore : Tells git which files or folder to ignore from the project — useful if you decide to include your app in...
Read more >create-new-svelte - npm Package Health Analysis - Snyk
The npm package create-new-svelte was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was ...
Read more >Rollup does not compile HTML from Svelte - Stack Overflow
The problem is that rollup, seemingly at random, does not generate the HTML and CSS files from the svelte-source files.
Read more >Build your Developer Portfolio and Blog from Scratch with ...
Using Svelte with GraphCMS means you can control the adding and ... A GraphQL query displaying the query on the left and the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m not sure I’d want
git init
run for me. I probably wouldn’t realize that had happened and am not sure what happens if you run it twiceShould we first ask people whether they want to use Git? (And default to yes.) And if they do, then not only create .gitignore, but also run git init for them? Even if they don’t plan on pushing anywhere yet, they can at least see in their editor which files are generated/ignored if the editor grays them out or whatever.