Closed laooola closed 4 years ago
@laooola Thank you for the PR! I'll try to get it merged within the next 2 days.
@danielr18 I'd probably do a new major release as this change won't work for next < 9.5.0
. Users on next >= 9.5.0
should use the new package version while users on next < 9.5.0
should stick with the previous one. This should also be documented somewhere e.g. in the readme?
@danielr18 I'd probably do a new major release as this change won't work for
next < 9.5.0
. Users onnext >= 9.5.0
should use the new package version while users onnext < 9.5.0
should stick with the previous one. This should also be documented somewhere e.g. in the readme?
Right, it'll be documented in the top section of the readme. Similar to how it was done for v3.0.0.
I encountered some issues with
Router.push
andRouter.replace
in combination with url objects after updating tonext@9.5.5
. Turned out that the internal router api has been changed in9.5.0
(see https://github.com/vercel/next.js/pull/14827). This PR accounts for these changes.