v2.0 Release Candidate - Migration Guide #1854
Locked
endigo9740
started this conversation in
General
Replies: 2 comments 2 replies
-
Regarding "Legacy Typography System", I was already using class="h1" etc.. In 1.x, fonts are thick. In 2.x, fonts are thin. I'm using the skeleton theme. Maybe there's something I'm not aware of. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Remember to include: plugins: [
require('@tailwindcss/forms'),
// ...
], into the tailwind config if using tailwind forms. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
*** Skeleton v2 is now live! ***
Migration Guide
If you would like like participate in testing the Skeleton v2 release candidate, please follow the instructions provided below.
Important
Unlike standard Skeleton releases, the v2 release candidate is designated as a
pre-release
, meaning there's a few extra steps to move fromv1.x
tov2 RC
. Please read and follow the instruction below very carefully.Using the Skeleton CLI
To install and test a new Skeleton v2 RC project using the Skelton CLI, use the
@rc
tag instead@latest
Migrating v1.x Projects
/src/app.postcss
/src/routes/+layout.svelte
Migrating your Tailwind Configuration
Next, we'll need to migrate
tailwind.config.cjs
to either a Typescript or Javascript format. If your project has Typescript enabled, use.ts
(Typescript) otherwise please opt for.js
(Javascript).Typescript (tailwind.config.ts)
Javascript (tailwind.config.js)
Migrating Themes
Theme configuration is now handled via your Skeleton Tailwind plugin settings in
tailwind.config
.Preset Themes
/src/app.html
and set your active theme via thedata-theme
attribute on thebody
element:Custom Themes
Skeleton themes now use a
CSS-in-JS
format. If you wish to migrate your v1.x theme, use one of the following techniques:Option 1) Use the Theme Generator
Recreate your theme using the updated Theme Generator, which provides themes in the new format.
Option 2) Migrate to the v2 CSS-in-JS format
:root
selector and paste them into the CSS field on the leftconverted
object, notconverted
itself).Create a new file in the root of your project, such as
my-custom-theme.[ts|js]
to house your new theme.Copy the following template into this file, then add your converted CSS-in-JS theme properties to the
properties
field:tailwind.config
and update your Skeleton plugin settings as follows:/src/app.html
and set your active theme via thedata-theme
attribute on thebody
element:Migrating Core Features
The following features include breaking changes that may affect your project.
Table of Contents
This features has been reimplemented from the ground up. We recommend you follow the updated documentation.
Drawer, Modal, and Toast Stores
We've refactored the stores for all singleton-based overlay features to help prevent known SvelteKit SSR issues. This includes two notable changes:
initializeStore()
in your root layout.View the documentation for each respective feature for more information:
Skeleton Data Tables
This feature has been completely removed in Skeleton v2. We now recommend Svelte Simple Datatables paired with Skeleton's Table Element styles.
Deprecated Autocomplete Props
The deprecated
whitelist | blacklist
props have been removed, please move toallowlist | denylist
respectivelyLegacy Typography System
The legacy "on-by-default" Typography system has now been completely phased out. Please migrate to the new opt-in system covered in the Typography documentation. In most cases this requires appending a single class to each typographic element.
Paginator Offset Prop
The
PaginatorSettings
parameter calledoffset
has now been renamed topage
for better semantics.Beta Was this translation helpful? Give feedback.
All reactions