Skip to content

LayerChart 2.0 (next)#449

Open
techniq wants to merge 285 commits intomainfrom
next
Open

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

Conversation

@techniq
Copy link
Owner

@techniq techniq commented Mar 10, 2025

No description provided.

@github-actions
Copy link
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 f60f482

@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 10, 2025

Open in StackBlitz

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

commit: f60f482

@changeset-bot
Copy link

changeset-bot bot commented Mar 12, 2025

🦋 Changeset detected

Latest commit: f60f482

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

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
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

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

@techniq
Copy link
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

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

@techniq
Copy link
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 Feb 18, 2026
github-actions bot and others added 8 commits February 18, 2026 09:56
* Version Packages (next)

* Update CHANGELOG for version 2.0.0-next.44

Updated CHANGELOG to reflect breaking changes, new features, and fixes in version 2.0.0-next.44.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Sean Lynch <techniq35@gmail.com>
Move @dagrejs/dagre to ssr.external instead of ssr.optimizeDeps.include.
The experimental ssr.optimizeDeps pre-bundling wasn't converting the
CJS module to ESM. Externalizing lets Node.js load it natively as CJS.
@github-actions github-actions bot mentioned this pull request Feb 19, 2026
techniq and others added 19 commits February 19, 2026 09:17
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* initial pass

* Fix typo

* Show star count

* Switch getDependents from runtime query to build-time prerender and parallelize GraphQL batch requests to reduce fetch time from ~44s to ~6s.

* pass built-in GITHUB_TOKEN when building for prerender()

---------

Co-authored-by: Sean Lynch <techniq35@gmail.com>
…n underline (from link status) between dl/month and d/l week. This fixes that. (#803)
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.

8 participants