-
Notifications
You must be signed in to change notification settings - Fork 39
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
Support Svelte 4 #111
Comments
Working with svelte 4 would be very useful. Last commit was 8 months ago. |
That's a good question, I already schedule a change to sveltekit after see this issue. Be sides exists the roadmap #19 |
I have forked the project (norricorp/svelte4-navigator), downloaded it and made changes. It compiles and I have used it in my project (which is also upgraded to svelte 4) and it all appears to work. |
I have commited to the forked repo and created a pull request to the part repo. |
Hello there ans thanks for the pr! Unfortunately i don't have a lot of time to work on the project, but i'll try to review your pr soon. There are quite extensive tests, you can run using the |
Hey guys, which other libraries for routing can you recommend? |
I migrated my app to SvelteKit and used its routing instead. Pain-free transition but took some time. Did it all in one big go.
-------- Original Message --------
…On Aug 28, 2023, 12:19, Visual-Dawg wrote:
Hey guys, which other libraries for routing can you recommend?
—
Reply to this email directly, [view it on GitHub](#111 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABGGVULLAEGRWSQHWVFV5QTXXRWD3ANCNFSM6AAAAAAZ2HSH7A).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I agree that svelte kit is the answer but I would like to get svelte navigator working with svelte 4 just because .... |
any solution? |
Unfortunately not. |
While SvelteKit seems to be the more future proof approach, svelte-navigator is just a nice library to implement on an existing Svelte project. Is there any perpective of updating it's Svelte dependency to version 4? |
Hi @pndiogo, I completely agree with your comment that svelte-navigator is just easier to use for an existing project. Certainly moving to sveltekit is a lot of work. If you would like to discuss further than am more than happy to email you directly. |
I think this project is died. owner should archive this repo so that everyone can understand. |
I already fork the project and try to learn more about it. anyone here already tried the project that's was forked? https://github.com/EmilTholin/svelte-routing This project seems continue be maintained |
UPDATE:
I realize your fork and PR solves this issue and your now just waiting on help from the current maintainer to get the integration tests to pass. In theory tho, is it possible to go ahead and use your override for those of us that don't want to wait on the PR merge (assuming our own risk of course). If so, do you have a commit hash you would recommend using with just the override and not all the testing mumble jumble? |
I used |
Any progress here on this issue? We struggle with the same problem |
This is what I'm using in our production app:
I've started working on a branch to migrate this package to Svelte 4+. It's partially done, but a decent amount to go. |
Unfortunately, it seems that svelte-navigator may be abandoned. I am currently switching to SvelteKit (with adapter-static) due to this... :( |
That was the conclusion I came to as well. |
Did you consider use the original https://github.com/EmilTholin/svelte-routing? This project is a fork from svelte-routing, may it's more easy to migrate. Sadly I didn't tried yet, but I'll pretty soon
|
I decided eventually to use Sveltekit but I do like the idea of navigator which does one thing. |
Currently svelte-navigator has a dependency on Svelte 3.x, which causes issues for projects wanting to upgrade to Svelte 4.
The text was updated successfully, but these errors were encountered: