You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey everyone, as you may be aware the Svelte v5 Release Candidate was recently announced at the Svelte Summit. We know many folks in the Svelte community are early adopters. As you may know, Skeleton v3 will be the first version of Skeleton to fully adopt all Svelte v5 features. For now, we want to provide a simple migration guide for your Skeleton v2 projects.
Should I Migrate?
In short, not yet. Neither Rich Harris or the the Svelte team recommend using Svelte v5 RC in production. The official recommendation is to begin testing migration on a dedicated feature branch. The Skeleton team matches this stance. However, we know many of you are going to do it anyways, so please follow this guide at your own risk!
Known Issues
Warning
We are working to resolve these known issues as soon as possible. If you rely on the <TreeView> component, do not migrate until the following issue is resolved in full.
Optional, but recommended: upgrade all of your project dependencies to their latest versions.
Update the Svelte package to the v5 RC: npm install -D svelte@next
Done!
Preparing for Skeleton v3
Please be aware that we expect and require the Svelte v5 stable release to arrive before the Skeleton v3. Given this, the best thing you can do right now is begin following the preparations listed below.
Preparing for Svelte v5
Note that all Svelte v4 APIs are backwards compatible in Svelte v5, which should provide a seamless migration, minus a handful of exceptions. However, please see Svelte's recommendation for migrating your local components and features to the new v5 APIs. This includes:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey everyone, as you may be aware the Svelte v5 Release Candidate was recently announced at the Svelte Summit. We know many folks in the Svelte community are early adopters. As you may know, Skeleton v3 will be the first version of Skeleton to fully adopt all Svelte v5 features. For now, we want to provide a simple migration guide for your Skeleton v2 projects.
Should I Migrate?
In short, not yet. Neither Rich Harris or the the Svelte team recommend using Svelte v5 RC in production. The official recommendation is to begin testing migration on a dedicated feature branch. The Skeleton team matches this stance. However, we know many of you are going to do it anyways, so please follow this guide at your own risk!
Known Issues
Warning
We are working to resolve these known issues as soon as possible. If you rely on the
<TreeView>
component, do not migrate until the following issue is resolved in full.Migrating to Svelte v5 RC
The following steps are identical, whether you're migrating from a brand new or existing application using Skeleton v2.x:
Tip
Run
npm list
in your terminal to check the exact versions of each dependency package you have installed.npm install -D svelte@next
Preparing for Skeleton v3
Please be aware that we expect and require the Svelte v5 stable release to arrive before the Skeleton v3. Given this, the best thing you can do right now is begin following the preparations listed below.
Preparing for Svelte v5
Note that all Svelte v4 APIs are backwards compatible in Svelte v5, which should provide a seamless migration, minus a handful of exceptions. However, please see Svelte's recommendation for migrating your local components and features to the new v5 APIs. This includes:
Questions or Comments?
Please reach out below if we can address any questions or comments you may have.
Beta Was this translation helpful? Give feedback.
All reactions