Svelte UX 2.0 (next) #571
Open
Svelte UX 2.0 (next) #571
+3,718
−3,061
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
|
|
🦋 Changeset detectedLatest commit: 69bc282 The changes in this PR will be included in the next version bump. This PR includes no changesetsWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
commit: |
* Initial migration to Tailwind CSS v4 using `npx @tailwindcss/upgrade` (and some manual tweaks) * Fix Gooey after bad tailwind upgrade * fix: Fix theme page (svelte-check) by adding `@reference '../app.css` * Format project (fix lint errors) * fix(docs): Fix blur input labels (@tailwindcss/upgrade) * Update `@layerstack/tailwind` and replace `tailwind.config.cjs` with css-based config * Remove custom theming page (for now) * Add changeset * Update `@layerstack/*` packages to `-next` (Tailwind 4) versions * Update tailwind 4 to latest * fix(TextField): refine classes to for tailwind 4 changes * docs(Gooey): Replace custom `bg-gradient-radial` with built-in `bg-radial` (tailwind 4)
* Version Packages (next) * Update CHANGELOG.md --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Sean Lynch <techniq35@gmail.com>
* Initial migration to Tailwind CSS v4 using `npx @tailwindcss/upgrade` (and some manual tweaks) * Fix Gooey after bad tailwind upgrade * fix: Fix theme page (svelte-check) by adding `@reference '../app.css` * Format project (fix lint errors) * fix(docs): Fix blur input labels (@tailwindcss/upgrade) * Update `@layerstack/tailwind` and replace `tailwind.config.cjs` with css-based config * Remove custom theming page (for now) * Add changeset * Update `@layerstack/*` packages to `-next` (Tailwind 4) versions * Update tailwind 4 to latest * fix(TextField): refine classes to for tailwind 4 changes * docs(Gooey): Replace custom `bg-gradient-radial` with built-in `bg-radial` (tailwind 4)
…f tailwind typography when deployed
* Version Packages (next) * Update CHANGELOG.md --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Sean Lynch <techniq35@gmail.com>
…untime separation
Merged
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* updated the get started page with tailwind v4 guide and added shell.nix file * Run `pnpm format` --------- Co-authored-by: Sean Lynch <techniq35@gmail.com>
… Add `data-level` attribute to li for CSS targeting
…rol via `classes`, `props`, `itemIndent` and `linkIndent` props and `link` slot.
Merged
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Merged
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Remove use of `$$props` (class, style) * Fix CI * feat: Support component icons (Unplugin icons, etc) and setup default icons on settings() for easy overriding. Change default to lucide * Remove unneeded @ts-expect-error * Update more locations * Update remaining components * Adjust Checkbox sizes * Update more examples * Update more examples * Update most remaining examples * Use app/state instead of app/store for page * Replace remaining @mdi/js usage and remove package * Cleanup * Fix types * Fix types * Increase the size of icon-only buttons * Update bluesky and discord icons * Switch back to page from `$app/stores` until full Svelte 5 migration occurs
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
No description provided.