Update .gitignore files in create-svelte package to ignore all dotfiles with a prefix of .env

[kellenmace]

Fixes #2904.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

[changeset-bot]

🦋 Changeset detected

Latest commit: 2d1d6a8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
create-svelte	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Conduitry]

IMO this should only add .env.*, if anything, and not .env*.

[bjon]

Shouldn't only env files ending with .local be ignored by default?
We're using vite's support for modes, e.g. .env.[stage|prod]

[Rich-Harris]

Thank you! Aside from the feedback above, can you reinstate the deleted checklist and add a changeset?

[kellenmace]

Thanks for the feedback, all! 🙌

@Conduitry - Sounds good. I updated the PR so that .env and .env.* files are git ignored. This way, on the off chance that the dev has some other file that begins with ".env" in their project, like ".envision", it won't be affected.

@bjon - Files like .env.local, .env.stage and .env.prod should generally not be added to version control. They often contain sensitive data like API keys. Devs should set their environment variables in their hosting provider's UI for their staging and prod sites. If a developer has a reason to want those included in git (which I wouldn't recommend), they can just tweak the .gitignore file to accomplish that. Next.js, for example, excludes those files in their .gitignore file for new projects, as well: https://github.com/vercel/next.js/blob/canary/examples/active-class-name/.gitignore#L27-L31

@Rich-Harris - Yes, checklist reinstated and changeset added. Please let me know if anything else is needed. 👍🏼