Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Release date/rough time estimate before React Router 6 will be released #7613

Closed
DeadManPoe opened this issue Sep 17, 2020 · 22 comments
Closed

Comments

@DeadManPoe
Copy link

DeadManPoe commented Sep 17, 2020

Is it possible to have a rough time estimate before React Router 6 will be released? I noticed it has been in beta 0 since January.

@MeiKatz
Copy link
Contributor

MeiKatz commented Sep 17, 2020

Good question. I also want to know this. But @mjackson and @ryanflorence are kind of silent in the last weeks and months.

@timdorr
Copy link
Member

timdorr commented Sep 17, 2020

They're working on Remix, so who knows.

@Zertz
Copy link

Zertz commented Oct 16, 2020

Don't let the pre-release tag stop you from using v6, it's an excellent release as-is! We have been using beta0 in production for a while now without any issues.

@beckerei
Copy link

For those of you who don't follow Ryan on twitter, or missed it: https://twitter.com/ryanflorence/status/1317168547064238081 and https://twitter.com/ryanflorence/status/1317215384710250497

So what @Zertz said 👍

@ancs21
Copy link

ancs21 commented Oct 19, 2020

@beckerei Good news.

Release v6 won't change API.

@joacub
Copy link

joacub commented Nov 15, 2020

wao it is been Lon long time..., next time I will think more before use react router next version, I was thinking they will release sooner.

btw good project.

@plandem
Copy link

plandem commented Nov 19, 2020

Release v6 won't change API.

yeah, but the funny part is - before matching was built around path-to-regexp package, but in v6 they gonna use their own implementation instead of that package.

@pshrmn
Copy link
Contributor

pshrmn commented Nov 19, 2020

@plandem, "v6 won't change API" is a reference from the current beta to release candidate.

@beckerei
Copy link

I hope it's okay to keep the thread updated with information from twitter.

Excited to get back to shipping React Router v6 stable soon. We know what it needs after using it to build Remix.

Better API, more features, and only 3.1kb over the network!

Far cry from v5 that's like 12kb or 14kb or something ridiculous (embarrassing?) like that.
https://twitter.com/ryanflorence/status/1337512362014752768

And some more

But we'll be bringing over some of the remix data loading APIs and other small features from Remix.
https://twitter.com/ryanflorence/status/1337517106007474176

@MeiKatz
Copy link
Contributor

MeiKatz commented Dec 15, 2020

@beckerei now @ryanflorence and @mjackson only have to merge the pending pull requests and change the confusing part with the root route definition. I mean, what the h**l is <Route path="/" /> and why is it not <Route path="" />? It's totally inconsistent!

@shulcsm
Copy link

shulcsm commented Dec 18, 2020

I have multiple projects blocked by #7423 and #7216. Second one seems to have a solid pull request.
How about merging what is merge-able and releasing a new beta for now?

@stale
Copy link

stale bot commented Feb 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
You can add the fresh label to prevent me from taking any action.

@stale stale bot added the stale label Feb 21, 2021
@dantman
Copy link

dantman commented Feb 22, 2021

😑 Should probably be marked fresh, an issue asking for when v6 will be released shouldn't be auto-closed
by a bot just because people are waiting for an update.

@stale stale bot removed the stale label Feb 22, 2021
@joacub
Copy link

joacub commented Feb 22, 2021

😑 Should probably be marked fresh, an issue asking for when v6 will be released shouldn't be auto-closed
by a bot just because people are waiting for an update.

I agree , is been one year since v6 beta

@evanheckert
Copy link

Recent tweet says hope is to release by Summer 2021. Also linked to transitions page referencing one of the remix features they intend to incorporate: https://gist.github.com/ryanflorence/fc67c2b689c5ecdca7185763a92f120a

@mariusmarais
Copy link

Given the dupes (my own included), can this issue maybe be pinned?

@pshrmn pshrmn mentioned this issue Apr 22, 2021
@Aarbel
Copy link

Aarbel commented May 12, 2021

@mjackson @timdorr i'm sure many developers would be thrilled to maintain this lib.

Can you open it to other maintainers ? This library is used by 2.1 million repos, and not updated since one year 🙏

image

@thecodejack
Copy link

Hi Team,

Is there any update related to v6. Has been betav0 for more than an year now with no releases. Would be interested to contribute if required to speed up the release

@remix-run remix-run deleted a comment from liho98 Jul 16, 2021
@remix-run remix-run deleted a comment from slk333 Jul 16, 2021
@mjackson
Copy link
Member

We are picking up work again on v6, should probably release within the next month or so. Thanks for your patience! It’s going to be the best work we’ve ever done on the router, I can promise you that.

@gsbelarus
Copy link

Is it possible to fix a basename issue first of all? As it is a show stopper for many who try to move existing projects from v5/v4. I mean PR:

#7462

May be do beta2 ASAP and other issues later?

@DennisBB

This comment has been minimized.

@chaance
Copy link
Collaborator

chaance commented Jul 28, 2021

Just an update on this, I'll be helping Michael on react-router full-time starting in a couple of weeks. A v6 major release is my top priority and I'm helping him organize/prioritize issues in the mean time. We appreciate your patience, but know that v6 stable is as crucial for Remix as it is for all of you, and we're very excited to roll it out soon. 🥳

I suspect you'll see one more beta with lots of known bug fixes, but we also need to finish up the docs so there's still a bit of work to be done. I'll try to keep this issue updated as we move in that direction.

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests