svelte-navigator VS bootstrap-vue

I went to the svelte-navigator github repo and they say that they support SSR. Now, if you use only ssr and not csr, that will reload the page on every navigation.That is because in ssr your front-end asks for entire page from server and doesn't just update components in front-end. For instance here they provide an example with ssr: https://github.com/mefechoel/svelte-navigator/tree/main/example/ssr

Well, depending on your project, you could try svelte-navigator.

But yeah, at the end of the day I guess the actual problem here is that the docs are more opinionated towards Sveltekit. I guess they're focusing on Sveltekit right now so I understand why they wouldn't want to maintain a whole separate project for the router like react, vue, etc right now. But maybe making the docs less opinionated and adding more examples for other use cases would be ideal. I ended up using svelte without sveltekit + this client router for svelte + golang and we are very happy with the results.

4. Bootstrap Vue Bootstrap Vue combines the power of Bootstrap, a popular CSS framework, with Vue.js. It provides a wide range of components and styling options. Check out the Bootstrap Vue website to learn more.

Vue (BootstrapVue)

You say that Afaik is the creator? I didn't see him listed as a major contributor on github: https://github.com/bootstrap-vue/bootstrap-vue/graphs/contributors . Do you happen to have his Github profile link?

For me personally one of the dealbrakers was bootstrap-vue still being stuck with Vue v2 / Bootsrap v4 to this day. react-bootstrap supports Bootstrap v5 since 2021 october.

Bootstrap-Vue: A UI library that provides a range of components based on the popular Bootstrap framework, including forms, buttons, and navbars.

BootstrapVue is the bundle: https://bootstrap-vue.org/

Yes. Please have the courtesy to feedback with a roadmap or prio of the issue. Especially for popular issues.

Asking, politely, for this should not label you as entitled freeloader. It is important input to make an informed decision wether one should just wait for the fix, workaround it, contribute a PR yourself, fork the component or drop it and consider alternatives.

One has to be careful with estimates though so they don’t become false promises. All respect to these maintainers but if I have to give one concrete example, consider following issue in a very popular Vue component, https://github.com/bootstrap-vue/bootstrap-vue/issues/5196 creating a upgrade deadlock for almost the entire Vuejs community. It’s the type of dependency that get so entrenched in everybody’s application that upgrading or moving away from it becomes very expensive and requires long term planning. As such, hundreds of comments there asking for estimates and also dozens of heavy names offering help in forms of PRs, forks or donations, all on a very polite level, but the maintainers kept promising it will be done “very soon” for almost 2 years straight. It appears the last months the war has been adding more obstacles so all respect for that, but even before the roadmap was hopelessly unpredictable.

I get it, as a volunteer other things in life often have higher prio, estimates tend to be optimistic and you might want to work on things in no particular order at all. What’s important is to be transparent, polite and communicate.

What's wrong with Angular? It being largely "batteries included" seemed pretty nice and I really liked the fact that TypeScript was a first class citizen - React and Vue both feel like it's been kind of tacked on, especially when a lot of additional libraries out there don't really have proper bindings.

That said, personally I also think that React kind of went downhill for a bit due to the hooks (after seeing a few projects become really nightmarish to debug due to render loops without clear causes for them, after people sprinkled one too many hooks in there).

Oh, and the Vue 2 to 3 migration is also a bit problematic because still many UI component libraries haven't been migrated over - currently actually using PrimeVue on a project because BootstrapVue still doesn't have proper support https://github.com/bootstrap-vue/bootstrap-vue/issues/5196