-
Notifications
You must be signed in to change notification settings - Fork 400
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
1.7.2 kills express when used with Express v4 Routers #156
Comments
max-degterev
changed the title
1.7.2 kills express
1.7.2 kills express when used with Express v4 Routers
Jun 17, 2014
see #154 |
@suprMax Yes, this is a duplicate of issue #154. I'm closing this issue out. We hope to have a fix out very soon. In the meantime, please continue using version 1.7.1. Thanks! |
cmcadams-newrelic
pushed a commit
to cmcadams-newrelic/node-newrelic
that referenced
this issue
Jan 29, 2024
…-app feat: AWS Bedrock example app
jsumners-nr
pushed a commit
to jsumners-nr/node-newrelic
that referenced
this issue
Apr 16, 2024
chore: added node 20 and drop node 14 in CI
bizob2828
added a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 19, 2024
update actions that are using deprecated node 12
bizob2828
added a commit
to bizob2828/node-newrelic
that referenced
this issue
Apr 23, 2024
update actions that are using deprecated node 12
bizob2828
added a commit
to bizob2828/node-newrelic
that referenced
this issue
Jul 26, 2024
chore: updated @newrelic/test-utilities to latest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi
After updating to 1.7.1 -> 1.7.2 I have the following issue:
Looks like it doesn't play nice with new Express routers, this is our base module class with encapsulated routes:
The text was updated successfully, but these errors were encountered: