-
Notifications
You must be signed in to change notification settings - Fork 41
TypeScript 6 compatibility #393
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
Open
rgieseke
wants to merge
6
commits into
mhkeller:main
Choose a base branch
from
rgieseke:ts-6-compat
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+75
−56
Open
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
7ecd534
Update Svelte packages
rgieseke 6c1f65a
Remove TypeScript 5 peer dependency and update to 6
rgieseke e04b3da
Update Action versions and use same Playwright image version
rgieseke 12fd6ab
Pin npm version more specific
rgieseke fe92aa5
Remove npm pin
rgieseke 68585cc
Update deprecated upload-artifact action version
rgieseke File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
engines.nodecurrently allows Node^20.17.0 || >=22.9.0, but the updated toolchain in this PR pulls in Vite 7.x which requires Node^20.19.0 || >=22.12.0(perpackage-lock.json). This mismatch can cause installs to fail under engine-strict setups or mislead users about supported Node versions. Consider bumping the engine range to match the strictest dependency requirement (or pinning Vite/@sveltejs/vite-plugin-svelte to versions compatible with the current engine range).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sveltekit has
Maybe we don't need to pin
nodeanymore in Layer Cake?