Skip to content

LayerChart 2.0 (next)#449

Open
techniq wants to merge 435 commits intomainfrom
next
Open

LayerChart 2.0 (next)#449
techniq wants to merge 435 commits intomainfrom
next

Conversation

@techniq
Copy link
Copy Markdown
Owner

@techniq techniq commented Mar 10, 2025

No description provided.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 10, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
layerchart ✅ Ready (View Log) Visit Preview 309b6df

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new bot commented Mar 10, 2025

Open in StackBlitz

npm i https://pkg.pr.new/layerchart@449

commit: 309b6df

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Mar 12, 2025

🦋 Changeset detected

Latest commit: 309b6df

The changes in this PR will be included in the next version bump.

This PR includes no changesets

When 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

@HicaroD
Copy link
Copy Markdown

HicaroD commented May 9, 2025

Hey, @techniq.
First of all, thank you for your amazing work, this package is actually incredible!

I have a question: When are you planning to merge this PR so we can finally get the Svelte 5 support? 🤗

@techniq
Copy link
Copy Markdown
Owner Author

techniq commented May 9, 2025

Hey @HicaroD, thanks for the kind words 🫶. Sorry, I don't have a rough release date set yet. There are a good number of improvements I would like to include in 2.0.0 (see milestone although not guaranteed to cover everything or have everything).

With that said, you 100% can use it today via layerchart@next and docs at https://next.layerchart.com/. I do this already for Github Analysis, Strava Analysis, and my main work project. It's also be used to build out shadcn-svelte Charts (issue).

I could see pushing some items to 2.1 but want to make sure if we find any breaking changes (mostly API refinements) we get them all in 2.0. I'm anticipating very little (if any), but still don't want to rush it.

Related: I also need to migrate Svelte UX fully over to Svelte 5 (it's Svelte 3-5 compat with Svelte 3/4 state/syntax). Both libraries have already been migrated to Tailwind 4, but the move to Svelte 5 state runes/snippets and regressions checking will take some concentrated efforts and time. I don't know how close I'll try to sync their release schedules though (and the benefit of having @next releases in place so they can be incrementally adopted).

@cycle4passion
Copy link
Copy Markdown

All the examples give 500 errors on https://next.layerchart.com/

@techniq
Copy link
Copy Markdown
Owner Author

techniq commented May 9, 2025

All the examples give 500 errors on https://next.layerchart.com/

@cycle4passion Odd... working here

image

Maybe try a hard refresh? Which browser?

@cycle4passion
Copy link
Copy Markdown

mobile only, does not work in arc (chromium), native chrome, or Safari browser.

@techniq
Copy link
Copy Markdown
Owner Author

techniq commented May 9, 2025

mobile only, does not work in arc (chromium), native chrome, or Safari browser.

Really odd... I can't reproduce

image

@github-actions github-actions bot mentioned this pull request Apr 17, 2026
techniq and others added 15 commits April 17, 2026 09:57
…recedence over the computed series fade opacity. Regression introduced by per-segment styling refactor where the explicit `opacity` was spread after `series.props`, clobbering per-series opacity values (e.g. `series={[{ props: { opacity: 0.1 } }, ...]}`).
…le series when no series are configured. Restores grouped layout for composable `<Chart>` usage (e.g. `<Bars>` with `x1`/`x1Domain`/`x1Range`) where the visible-series filter previously emptied the secondary band scale domain, collapsing all bars to a single category position.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…n `release: published`, add `generate:releases` to `prebuild` (and `generate:all`) so each build pulls the latest from the GitHub API, and have the script use `GITHUB_API_TOKEN` to avoid the unauthenticated rate limit.
…(`src/generated/api/` → `generated/api/`, `src/content/releases/` → `generated/releases/`) — this also keeps mdsx's `.md` preprocessor away from the release files, which was choking on `{`/`}` in arbitrary GitHub release-note text.
- this fixes the previous issue on Steps where too little space between left col of circled numbers/line and right content header text. When you hovered the header line the popup link icon overlapped the circle.

- also better aligned circles w/header text.

- fixed checkmark as last content of circle.
- fixed some wording
- adding note referencing setup darkmode
- cleaned up content to 'git up and running quicker' tabs
bestMatchRank now tokenizes the query, requires every token to appear in the haystack (title + component name for examples), and requires at least one token in the title — so e.g. "tree playground" or "playground tree" promotes the Tree/playground example to "Best match" while keeping long-content guides whose titles don't match out of the top group.

getSnippet and highlightMatch now operate per-token: the snippet anchors on the earliest token hit and all tokens are highlighted via a single alternation regex.
Examples can now declare search keywords via `export let tags = [...]` in their `<script module>` block. The catalog generator picks them up (also accepting `export const`), threads them through to the search index, and includes them in the "Best match" haystack alongside the title and component name — so e.g. tagging the Tree playground with `['tiger']` makes it discoverable by that keyword.
…rops to be treated as pixel values instead of data property names
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants