You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on the New Relic Node.js agent team and there was a release of [email protected] this week that broke some of our tests. We fixed them because path-to-regex was upgraded to 8.x. However last night @koa/router released 13.1.0 and the path-to-regex package was reverted to 6.x. I thought these packages were supposed to be identical. We can totally handle this nuance but jsut wanted to get confirmation from you all if this was intended?
The text was updated successfully, but these errors were encountered:
bizob2828
changed the title
[fix] koa-router and @koa/router are on different versions and different versions of path-to-regex
[fix] koa-router and @koa/router are on different versions of path-to-regex
Sep 18, 2024
We are reverting path-to-regex from version 8 to version 6 due to the challenges and significant impacts that version 8 poses for many consumers. We are not yet prepared to provide guidance or support for this transition. We plan to address this in a future major release, likely version 14.
Note: The bump to version 8 occurred due to a typo.
About the koa-router, I am waiting to get access to be able to publish these versions: 12.0.2 & 13.1.0.
Hi, thanks 3imed-jaberi for the informations.
Can you tell when the newer versions of koa-router 12.0.2 and 13.1.0 with Path to Regex 6.3.0+ will be published?
Describe the bug
I'm on the New Relic Node.js agent team and there was a release of
[email protected]
this week that broke some of our tests. We fixed them becausepath-to-regex
was upgraded to 8.x. However last night@koa/router
released13.1.0
and the path-to-regex package was reverted to 6.x. I thought these packages were supposed to be identical. We can totally handle this nuance but jsut wanted to get confirmation from you all if this was intended?The text was updated successfully, but these errors were encountered: