-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow typescript configuration files #4105
Conversation
🦋 Changeset detectedLatest commit: 537c2a7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
We just had a similar PR #4031 a while ago and got closed because we want to resort to sveltejs/rfcs#59 moving forward. Further reasons are noted at #4031 (comment), so unfortunately this won't likely be merged. |
ahh too bad. |
I am reopening, because this PR introduces none of the problems in the discussion you linked above. Except for using an external package. However, it works perfectly. |
It introduces compatibility issues with language tools and vite-plugin-svelte no? They can't load svelte config in typescript. |
Not that I can see... EDIT: actually yes, it does, see my next comment |
so vite plugins and aliases are not found. |
I guess I just didn't look close enough. |
Still I believe that updating accordingly the language tools shouldn't be that much of a deal |
This PR adds the possibility to use typescript configuration files, and makes use of this in the docs website.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpx changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0