Skip to content
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.

Support React Router v4 / React 16 #19

Open
igorify opened this issue Oct 3, 2017 · 10 comments
Open

Support React Router v4 / React 16 #19

igorify opened this issue Oct 3, 2017 · 10 comments

Comments

@igorify
Copy link

igorify commented Oct 3, 2017

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!

@igorify igorify changed the title Support React Router v4 Support React Router v4 / React 16 Oct 3, 2017
@hmdhk
Copy link
Contributor

hmdhk commented Oct 4, 2017

Hi @igorify ,

Thanks for reaching out!
Currently we're making major improvements to our product. However this also means it takes more time for us to release support for new versions.
We haven't finalized a timeline yet, But I will make sure that we send out announcements when that happens.

Cheers,
Hamid

@Crash--
Copy link

Crash-- commented Oct 17, 2017

It can be great to have React 16 supports. Just spend 15 minutes to understand why, in build mode, my app started to crash. :(

@danieljuhl
Copy link

@jahtalab any news on this one?

@hmdhk
Copy link
Contributor

hmdhk commented Nov 23, 2017

@danieljuhl ,

Thanks for reaching out.
Unfortunately no updates yet.
We're currently working on integrating our APM product into Elastic stack.

Cheers

@danieljuhl
Copy link

@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)

@hmdhk
Copy link
Contributor

hmdhk commented Nov 23, 2017

@danieljuhl ,

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.
As for the timeline we're still working on it. However we're going to send announcements about the timing as well as instructions to migrate the agent.

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.

@daviestar
Copy link

@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.

@hmdhk
Copy link
Contributor

hmdhk commented Jan 15, 2018

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

@bogdan-calapod
Copy link

So, currently, there is no way to use Opbeat with React 16 at least ? (without the router)

@hmdhk
Copy link
Contributor

hmdhk commented Feb 1, 2018

Thanks for reaching out @bogdan-calapod,

If you only need error logging, you can use our Plain JavaScript agent which is framework independent.
Otherwise, unfortunately our react agent doesn't support React 16.

Cheers

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants