Skip to content
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

breaking: svelte-check v4 #2453

Merged
merged 12 commits into from
Aug 27, 2024
Merged

breaking: svelte-check v4 #2453

merged 12 commits into from
Aug 27, 2024

Conversation

dummdidumm
Copy link
Member

@dummdidumm dummdidumm commented Jul 31, 2024

closes #2243

WIP, will finish after my vacation.

},
"peerDependencies": {
"svelte": "^3.55.0 || ^4.0.0-next.0 || ^4.0.0 || ^5.0.0-next.0"
"svelte": "^3.55.0 || ^4.0.0-next.0 || ^4.0.0 || ^5.0.0-next.0",
"typescript": ">=5.0.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we support some versions of Typescript 4? It might be nice for users who haven't been able to upgrade yet if it's not too hard for us

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reminding me to bump the Svelte peer dependency to v4 😄 And since v4 has an implicit dependency requirement on TS >=5 we should, too. Better to nudge users towards upgrading

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think users will have plenty of reason to upgrade on their own since Svelte 5 is so much better. But it'd probably be appreciated if we let them do it in their own time instead of forcing them. It can make things easier to have wider support as you have more flexibility around what order to upgrade various libraries

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't forcing people to jump to Svelte 5, only Svelte 4 - which you need to do before upgrading to 5 anyway.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, I know. I was just saying people would want to upgrade to Svelte 4 in order to get to 5 so we don't need to push them too hard

devDependencies pinned to Svelte 3 because other packages in this repo still use it. Theoretically we still support Svelte 3 with svelte-check v4 but this gives us the opportunity to adjust that later without a major
@benmccann
Copy link
Member

Is @jridgewell/trace-mapping unused? It looks like maybe we could remove it?

@dummdidumm
Copy link
Member Author

No it's used within the language server

@benmccann
Copy link
Member

No it's used within the language server

It should just be a dependency in that project then and not svelte-check, right?

@dummdidumm
Copy link
Member Author

dummdidumm commented Aug 20, 2024

No, the setup here is a bit different, we're bundling most of the language-server package but externalize a few dependencies, which we then need to require separately.

@benmccann
Copy link
Member

Just curious, how is it decided which are bundled or why can't we bundle @jridgewell/trace-mapping?

@dummdidumm dummdidumm marked this pull request as ready for review August 27, 2024 10:23
@dummdidumm dummdidumm merged commit d6a2031 into master Aug 27, 2024
3 checks passed
@dummdidumm dummdidumm deleted the svelte-check-major branch August 27, 2024 10:37
@dummdidumm dummdidumm restored the svelte-check-major branch August 27, 2024 10:38
@dummdidumm dummdidumm deleted the svelte-check-major branch August 27, 2024 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

svelte-check breaking changes v4
2 participants