-
Notifications
You must be signed in to change notification settings - Fork 404
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
Express 4 Support #132
Comments
It's in progress! It would be very helpful if each major version of Express weren't a nearly total rewrite, but such is life. Thanks for opening this issue! |
👍 Yes Please |
@othiym23 Is there any ETA with respect to supporting Express 4x? |
In the mean time if you just want simple transaction tracking you can use some simple middleware: app.use(function (req, res, next) { |
Thanks @geekatron for redirecting #138 this way. Also thanks @mfasanya for an excellent suggestion on a workaround. While I personally love using Github for reporting and fixing bugs, feature requests done through here won't be as powerful as through http://support.newrelic.com. As our customer base grows, the support channel becomes our primary funnel for prioritizing feature development. I will keep this ticket updated! |
You were the one that told me to put it here ;) |
@ChiperSoft heh, I'm full of lies! =] Seriously though, I think having this ticket is great, I just wanted to make sure people know where their voice for feature development is loudest. |
Hello folks! I have good news for everyone who is running express 4. Express 4 is the poster child for our new feature flags. In development/staging you can add the following to your feature_flag: {
express4: true
}, This will turn on express 4 support. Keep in mind, this is not super battle hardened, and we don't recommend you run it in production. If you run into any issues, please let us know at http://support.newrelic.com/ with your logs attached so we can analyze them. Thanks! |
Any ETA on Express 4 support getting merged into master? |
I think it already is there. I've updated to the latest build and the route names are coming through. |
It is on master behind the flag, supposing everything goes well, we hope to
|
This has been generally released in version |
🤘 😻 🤘 |
Is it to be turned on using the feature flag? or is it by default? I am using still not capturing transactions - all captured on /* |
@sarath I think your issue will be best handled through http://support.newrelic.com |
…/graphql-koa-dataloader/app/graphql-16.8.1 chore(deps): bump graphql from 16.6.0 to 16.8.1 in /graphql-koa-dataloader/app
Bumps tap and resolves audit warnings
Bumps tap and resolves audit warnings
…3fb3d49fb60c73da6b [Snyk] Security upgrade newrelic from 10.0.0 to 10.3.1
At @groundwater's recommendation, opening a ticket to track Express 4.0 support, since I'm using it for mash.li.
The text was updated successfully, but these errors were encountered: