-
Notifications
You must be signed in to change notification settings - Fork 8
Support React Router v4 / React 16 #19
Comments
Hi @igorify , Thanks for reaching out! Cheers, |
It can be great to have React 16 supports. Just spend 15 minutes to understand why, in build mode, my app started to crash. :( |
@jahtalab any news on this one? |
Thanks for reaching out. Cheers |
@jahtalab a quick follow up. Will the Elastic APM React agent be compatible with Opbeat? And when is such an agent planned for (with support for React 16) |
We have made changes to our API (as well as other changes) therefore Elastic APM agents will not be compatible with Opbeat's intake API. P.S. You should already have some of our announcements about joining forces with Elastic and the progress so far, If not, be sure to subscribe to our mailing list. |
@jahtalab is there any update on this? even a vague timeline. our initial investigation into opbeat was great and we're hoping to roll it out across all our projects but this is blocking us. |
Thanks for reaching out @daviestar and sorry about the slow response. Unfortunately no updates on this yet. As you know we're in the process of moving our product to elastic stack. Our first frontend agent (Which is going be released into alpha soon) works with pure JavaScript and it's not framework specific. You can find out more here. Going forward we will address these issues as we release framework specific plugins. Cheers |
So, currently, there is no way to use Opbeat with React 16 at least ? (without the router) |
Thanks for reaching out @bogdan-calapod, If you only need error logging, you can use our Plain JavaScript agent which is framework independent. Cheers |
Hi, guys!
If I use react-router v4, what should I do?
When you provide the support of React Router v4 and React 16?
Thanks!
The text was updated successfully, but these errors were encountered: