Svelte 5 migration #21
Open
Conversation
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
Merged
|
hi @accuser is there any progress on this? this is the only thing blocking me from migrating to svelte 5 so just wondering? (sorry if this is not the place to ask that, thought opening an issue is too much) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've started to think about
<PlausibleAnalytics />in terms of Svelte 5. Here is a first pass.I'd originally intended to make use of
plausible-trackerinstead of the<svelte:head />script insertion, but plausible/plausible-tracker#60 is a blocking issue. I've retained the dependency for types only at this time.