tinro
tinro copied to clipboard
AlexxNB
Is this project still active?
I think not. I've opened https://github.com/AlexxNB/tinro/issues/122 and I think several months without an update means the project is indeed inactive :sweat:
Well, that's disappointing, it's over a year now. Because tinro is good.
svelte-routing, svelte-spa-router both redirect to SvelteKit. SvelteKit and Routify use what I would describe as "unacceptable" naming conventions and seem to be designed for hacking together hand coded blogs or something. Nothing wrong with that, I'm in favor of opinionated, but with all Svelte users being pushed hard towards SvelteKit it has now killed all non-SvelteKit packages, those opinions are becoming an issue. (My opinion is that SvelteKit is not anything like as cool as it thinks it is, FWIW.)
Proposal: for Svelte to survive other than as a bullet point in SvelteKit, sombody will need to fork one of these routers and merge some PRs...
Well, that's disappointing, it's over a year now. Because tinro is good.
svelte-routing, svelte-spa-router both redirect to SvelteKit. SvelteKit and Routify use what I would describe as "unacceptable" naming conventions and seem to be designed for hacking together hand coded blogs or something. Nothing wrong with that, I'm in favor of opinionated, but with all Svelte users being pushed hard towards SvelteKit it has now killed all non-SvelteKit packages, those opinions are becoming an issue. (My opinion is that SvelteKit is not anything like as cool as it thinks it is, FWIW.)
Proposal: for Svelte to survive other than as a bullet point in SvelteKit, sombody will need to fork one of these routers and merge some PRs...
True I did the same message in svelte routing repo https://github.com/EmilTholin/svelte-routing/issues/236#issuecomment-1453231120
Hi I forked svelte-routing > https://github.com/krishnaTORQUE/svelte-routing-next. And I merged most of the PR from origin repo. Please let me know if you have any query. Thanks.
FYI, looks like svelte-spa-router is active, (they removed the "use SvelteKit" warning!) so that might also be worth looking into. It really doesn't help that there are many alternatives with similar names, oddly the "don't use this" options all come up first in search and the "active" ones don't show at all. Undoubtedly due to the nature of how LLM neural nets collapse similar words, but it's still a bug. But I digress.
Navigo is pretty spiff--not integrated, but also not svelte-speicific. Useful if you're in an eval phase and not entirely sure which template engine you will end up with (or in my case, wondering if SvelteKit is going to eat Svelte and I'll be porting again in 3 years). For people who are not a fan of the Kit/Routify style routing, it's the exact opposite. :)
(Also, apologies to the repo owner for our discussion of alternatives in a support thread...)
I just posted something similar at https://github.com/EmilTholin/svelte-routing/issues/236#issuecomment-1511942236
Basically I'd like to see the community get behind a unified effort towards having a defacto declarative router for Svelte. I think what @krishnaTORQUE has done is a great start. While svelte-spa-router removed their warning, they still aren't touching their pr backlog - and also I prefer to not have my routes declared as an object, but as components because it feels more natural.
Rather than all these projects pointing to SvelteKit (which is great for some things, but falls short on many use cases) it would be better if there was a declarative option perhaps with a few maintainers so it's not all on one person.
Clearly such a project is needed. We just need to get everyone working in one direction.
FYI, looks like svelte-spa-router is active, (they removed the "use SvelteKit" warning!) so that might also be worth looking into. It really doesn't help that there are many alternatives with similar names, oddly the "don't use this" options all come up first in search and the "active" ones don't show at all. Undoubtedly due to the nature of how LLM neural nets collapse similar words, but it's still a bug. But I digress.
Navigo is pretty spiff--not integrated, but also not svelte-speicific. Useful if you're in an eval phase and not entirely sure which template engine you will end up with (or in my case, wondering if SvelteKit is going to eat Svelte and I'll be porting again in 3 years). For people who are not a fan of the Kit/Routify style routing, it's the exact opposite. :)
(Also, apologies to the repo owner for our discussion of alternatives in a support thread...)
FYI svelte-spa-router uses hash based routing which is not good at all for SEO where svelte-routing history based or in simple, actual routing which is recommended for SEO.
+1 "hash routing only" is a big negative, even if you don't care about SEO.
+1 "hash routing only" is a big negative, even if you don't care about SEO.
But it's also an absolute requirement in many cases, namely when you don't control the entire page and the path cannot be modified, only the fragment.
Typically if you write a svelte app that runs inside of a CMS such as WordPress, Joomla, etc
That's a lot of applications and SvelteKit or all the usual svelte routers cannot be used in this context.
