devise-token_authenticatable | gem provides the extracted Token Authenticatable module | Authentication library

You just shared the Gem file, but nothing how this app is developed, so it is insufficient information to give you an accurate response. But usually, two different methods are followed.

Two separate application, as your ruby on rails application working, can create another react application, and consume all endpoints present in your Ruby on Rails application, if you could not find some require endpoint, you can check already made endpoints and make few new one following the way. Hopefully, it would be easier to do.

In this method, you have to break apart your project and removing all Angular Gems already present in your project and start with fresh frontend with ReactJS. In my opinion, it requires much more Ruby on Rails knowledge to do it, but in the end, you will get just one project.

As from Gem file seem it is heavily using Angular, so probably you have run it and check if it has most of the Endpoints made Restful. If yes then I suggest to go on method one and create new ReactJS app, which will consume all endpoint made in Ruby on rails, that would be more work on React side app and less on Ruby on Rails. Even if you found that some endpoints are not present you can follow already created endpoints coding and action, where you will complete details. I understand there will be two different projects, but the learning curve to learn Ruby on Rails and integrating it with React would be more than having two different projects.

This issue may reveal something to you:

https://github.com/activerecord-hackery/polyamorous/issues/34

After reading it, I would grep through your project for references to make_constraints, as it seems something has changed in 5.2 with regard to it that would lead to a similar error.

Or, if you see the polyamorous gem in your Gemfile.lock, problem solved, just update the gem as they fixed it in January.