chore: overhaul ignore configs

[hyunbinseo]

This is a recreation of the following issue. Sorry for the inconvenience.

• chore: overhaul ignore configs #11881

Notable Changes

1. Follow the Vite's .env file conventions - only the *.local files are ignored by git.
2. Clean-up of .eslintignore - removal of JSON, YAML, and env files from the list

Note

JSON and YAML files are not handled by ESLint - plugins have to be installed.

Additional Suggestions

.gitignore

1. Merge different ignore files into one. Suggestion below:
2. Remove .output and .vercel from the default ignore file.

/package
node_modules

# Output
/.svelte-kit
/build
/dist

# OS
.DS_Store
Thumbs.db

# Vite
.env.*.local
.env.local
vite.config.js.timestamp-*
vite.config.ts.timestamp-*

---

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 pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 3731426

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

[hyunbinseo]

@benmccann your suggestions have been applied. What do you think about merging (unifying) the .gitignore files?

[benmccann]

What do you think about merging (unifying) the .gitignore files?

I don't have a strong feeling one way or the other. I don't really understand why they're different at the moment

[benmccann]

wouldn't this be considered "Output"?

I think if you changed the "Lockfiles" head to "Package managers" then you could put node_modules there too

[hyunbinseo]

I wasn't certain about the /packages directory. When is it used? The package template uses the dist directory.