Remove lodash-es dependency

[es3n1n]

#616

Blocked by techniq/layerstack#95, once its merged i'll need to bump the versions in package.json + remove extra case for get with a number

[changeset-bot]

🦋 Changeset detected

Latest commit: e3253fa

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

This PR includes changesets to release 8 packages

Name	Type
shadcn-svelte-1	Patch
svelteux-2	Patch
skeleton-3	Patch
skeleton4	Patch
standalone	Patch
layerchart	Patch
daisyui-5	Patch
docs	Patch

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

[pkg-pr-new]

Open in StackBlitz

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

commit: 017c84f

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
layerchart	✅ Ready (View Log)	Visit Preview	017c84f

[techniq]

Thanks @es3n1n, I'm taking a look now. Currently throwing a stack track when rendering all the LineChart examples I'm trying to identify the root cause

[techniq]

@es3n1n actually this looks to have been introduced upstream in state-refactor (which makes sense as it's still very actively being developed. I'm going to stack this PR up a branch onto docs-v2 instead of state-refactor and if all looks good, we're merge into doc-v2 and I'll pull those changes up into state-refactor. Sorry for the noise.

[es3n1n]

Ah, I see. Do you want me to rebase to docs-v2 so that it will be easier to merge later?
I clicked through some examples while testing locally, but apparently LineChart was not among them :p

[techniq]

@es3n1n I have the rebase completed locally (with a little Claude help to make sure I didn't screw it up 🤣) but looks like you'll need to perform the rebase on your fork

Could you rebase locally onto docs-v2 (fwiw I used: git rebase --onto origin/docs-v2 origin/state-refactor pr/es3n1n/734).

... you just replied 🫶. Yes please 😃

[es3n1n]

Completely missed that notification, but I think we're good to go now!

[techniq]

Thanks, and great work!

I was able to tease out an error here and there, but would always disappear after a refresh (or loading the example directly) which is not uncommon with Svelte async / remote functions at the moment.

Example:

Going to merge and keep an eye on any regressions. I also plan to regenerate all 700 example screenshots soon which should give a good indication if we've overlooked any regressions.

Thanks again!