-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of svelte/internal in Svelte 5 #5707
Comments
After going through some PRs, I found that this issue should be fixed with some upcoming update. |
I have tested it with |
Be aware that some breaking changes will be coming to the alpha soon though. And we don't have the v9 alpha docs visible on the TanStack website yet, but they can be browsed on GitHub. |
I didn’t test the alpha and I didn’t know it was under development, sorry for that :) according to @KevinVandy I better not implement it for now so I will wait for the official release. Thank you all for the good work |
You can use it, you just might want to pin the version and make sure you only upgrade intentionally. |
I just updated TanStack Table to alpha.10, applied all the new changes and it is rendering👍🏻 let options: TableOptions<any> = $state({
data: defaultData,
columns: defaultColumns,
getCoreRowModel: getCoreRowModel()
});
const table = $derived(createTable(options));
Nvm 😄 |
If anyone's looking for a drop-in replacement that largely keeps the old API of |
TanStack Table version
8.20.1
Framework/Library version
Svelte 5
Describe the bug and the steps to reproduce it
This is not related to the use of runs in Svelte 5 or migrating the current TanStack's codebase to Svelte 5 as it should be working fine with Svelte 4.
It is about the use of
svelte/internal
as it is no longer supported in Svelte 5 which will make TanStack unusable and a migration blocker to projects depending on it.Originally posted by @dummdidumm in sveltejs/svelte#12104 (comment)
Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://svelte-5-preview.vercel.app/#H4sIAAAAAAAACmWNwQrCQAxEfyXkUoVK76WKfoO9WQ_rNoXFbrJsUkFK_11avXl8M8ObGYcwkmJ9m5FdJKzxkhKWaO-0gr5oNMISVabs16RRn0OyU8chJskGM_hMzui6TVv3GAkWGLJEKM7mWM35Z_UVHWyti469sBpsBMd_wU6SBWHdd9xUv0MsMUofhkA91pYnWu7LBxTLfES_AAAA
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
None
Terms & Code of Conduct
The text was updated successfully, but these errors were encountered: