Is it safe to use on production?
Hey guys, maybe this is a stupid question but the only reference to that this package might be "unsafe" to use is with "BETA" in logo and npm package link. No info on github, website, anywhere, or at least I can't find it. So, is it relatively safe to use on production or some braking changes without new major version may happen?
EDIT: Even here with searching through questions I can't find anyone asking about it :x Is the "beta" so obvious for everyone but me? 😅
5 Replies
fair-rose•3y ago
Honestly, the beta is currently in quite a good place.
Tanner's push today, has brought some excellent changes and quite frankly I'd be comfortable using it.
That being said, I've been actively using the library for nearing two months now, and understand it well enough to use it without the full documentation. Currently, if you are willing to dive into the example projects at the bottom of the docs, and be willing to figure it out, I'd say look at getting ready to move your SPA over to this.
However, you can't ignore the
beta tag, and with it comes the possibility for some 'unexpected changes' to be just around the corner. Case-in-point today's release.
If you really don't want to have to make changes to your codebase once shipping this router, then maybe it's best to wait till it goes 1.0... but if you are willing to put in the work after the fact, to patch in any changes, I'd highly recommend you play around with this Router.
Its truly unlike anything I've ever used before.rising-crimsonOP•3y ago
It all sounds great, but if I'm about to create a stack for newest client's project with whom I might separate my ways in next 4-5 months, it doesn't sound very secure to use it then :x For my personal projects I would for sure but I need to take into account leaving the code at it is after some time and not risking it to fail the next day without overseeing :x So sadly I think I will have to stick with react-router this time, unfortunately 😢
fair-rose•3y ago
Yup that's fair.
I'd still say give the beta a play-around though. I'm pretty sure Router is getting tested by Tanner in production with Nozzle, and it is in a pretty good place.
sensitive-blue•3y ago
I'll be using it in production here shortly!
extended-salmon•3y ago
We have been building an app with this library for a few months now. So far so good, but there are some important features that we have been missing lately:
- A built-in ability to scroll on top when a new route is loaded. Discussion: https://github.com/TanStack/router/discussions/299
- A way to render a 404 component when exact match is not found. There is an issue on GitHub: https://github.com/TanStack/router/issues/484
- A built-in way to render a custom confirmation message and prevent routing in certain scenarios. Discussion: https://discord.com/channels/719702312431386674/1071351569376874496
GitHub
Scroll Behavior on page change · Discussion #299 · TanStack/router
Hello, I wonder if it would be ok/useful to have an option in router to allow scroll behaviors. for exemple => keep current scroll on page change always go to top on page change I couldn&...
GitHub
defaultComponent is never rendered if exact match is not found · Is...
Describe the bug I have defined defaultComponent that should be rendered when exact route match is not found: const router = createReactRouter({ routeConfig, defaultComponent: NotFound, }); Now if ...