chore: overhaul ignore configs

[hyunbinseo]

Update git, Prettier, and ESLint ignore files.

1. Sort items alphabetically.
2. Categorize items into OS, Vite, and Lockfiles.
3. Remove the leading / - match the style with the node_modules entry.
4. Follow the Vite's .env file rules - only the *.local files are ignored by git.
5. Remove items from .eslintignore that are not handled by ESLint, such as .DS_STORE.
6. Add items to .eslintignore, such as dist which is generated in the library template.
7. Add Thumbs.db for Windows users.

---

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]

⚠️ No Changeset found

Latest commit: 41bb2c0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[benmccann]

I think it could lead to trouble to remove the leading /. If the user has something like src/packages/package as we do in SvelteKit it would end up getting ignored, which isn't what we want

[benmccann]

build and .svelte-kit are both output, so should be grouped together.

Suggested change

[benmccann]

are we sure eslint ignores these files? how do we know that?

[hyunbinseo]

JSON and YAML files are not formatted by default.

Plugins have to be installed:

• JSON: https://github.com/kuceb/eslint-plugin-json-format
• YAML: https://github.com/ota-meshi/eslint-plugin-yml

And the extensions should be provided in the CLI and configuration.

[benmccann]

If I recall, the reason this was ignored was that people were worried about accidentally checking in production secrets. It makes sense to me to ignore it because you're not going to check it in here, but will instead provide it as part of your production deploy

[hyunbinseo]

Ignoring the .env file goes agaist the Vite convention.

https://vitejs.dev/guide/env-and-mode#env-files

.env                # loaded in all cases
.env.local          # loaded in all cases, ignored by git
.env.[mode]         # only loaded in specified mode
.env.[mode].local   # only loaded in specified mode, ignored by git

Since SvelteKit is at it core a Vite project, following this seemed intuitive.

Especially since .env.test and .env.test.local files are utilized by Vitest.

[hyunbinseo]

@benmccann I am really sorry, I badly messed up my git branching.

Should I create a new PR with the above mentioned suggestions?

[ghostdevv]

Go for it @hyunbinseo