chore: delete "moduleResolution": "bundler" from tsconfig and jsconfig

[huseeiin]

Delete "moduleResolution": "bundler" from tsconfig and jsconfig as its already in the tsconfig located at "./.svelte-kit/tsconfig.json"

---

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: dc81574

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

[dummdidumm]

Why remove it? I don't think we should do that.

[eltigerchino]

I was also thinking of removing it but it’s probably better to not remove it because the generated config only exists after the user runs vite dev, etc.

[dummdidumm]

Oh right it's part of the generated config by now. Mhm..

[dominikg]

i actually wonder if we should encourage commiting the generated config instead of ignoring it.
Remembering to run sync when switching branches is a bit of a pain.

[benmccann]

I actually wonder if we want to go the reverse direction and set NodeNext in the generated config and then have all apps set bundler. It can be very disruptive to the ecosystem when libraries don't set NodeNext. There's not a lot of harm if an app does that except for annoyance at extra work, but things don't break in the same way that they do if a library sets bundler then potentially affecting all of its dependencies.

E.g. check out the Threlte instructions at https://threlte.xyz/docs/learn/getting-started/installation which have a needless step in their setup instructions because they're missing the moduleResolution that we ship by default for libraries (threlte/threlte#985):

[benmccann]

I'm going to go ahead and close this since the templates have moved to https://github.com/sveltejs/cli