Is vender lock critical using next.js?

Question

Ruby on Rails

Hello!
A question that has been haunting for weeks now!
First, about our stack:
Backend: Ruby Rails, Spree,
Frontend: React, Redux, Redux Thunk
We decided to write an online store using React and SSR. There was a question what ready technology to take, for this business.
For Ruby Rails, there is a wonderful react-rails gem in which, supposedly, everything is already there for writing a full-fledged application with friendly SSR.
But everything turned out to be not so wonderful. Some libraries do not want to work with node.js, and redux starts up with dances, and react-rails debugging with ssr enabled is impossible. We turned to the developers, to which we received a wonderful answer "Sorry, for now it's the only way ..."
We decided to create our own SSR using the express server. It turned out to be a hemorrhoidal and long undertaking.
And then next.js caught my eye! From the first minutes of dating, fell in love! Super fymvork, what you need. There is routing and adequate work with redux and automatic ssr. Hooray!!
But!!!!!! It's a framework!!
Looking at the crazy branch of releases, when a new update is released almost every day and almost every one has major updates, I thought ...
The framework is suitable for us, just take it, install it and have fun, but won't it be a fatal vender lock when through a couple of months the project will cease to be supported or something else interesting will happen.
In short, the question is:
Who worked with next.js share your opinion? How much does it cost to depend on this framework in the future for the project?

Answer 1

I used nextjs myself, everything is very cool, nothing needs to be configured, there is support!
I had a problem, I used socket.io with nextjs, gave an error, opened an issue in github and immediately support went and the problem was solved.

Answer 2

The master has not been updated for two months. You've probably looked at the canary branch.