fix: support express@5 router

[wesleytodd]

Fixes #57, although I did not see the same error as reported. This does get the tests passing in with express@5 though.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, filesystem, network Transitive: eval	+48	1.71 MB	dougwilson

View full report↗︎

[Megapixel99]

The check for node 14 seems to be stuck on npm it (unsure if express 5 supports node 14), the code looks good though.

[wesleytodd]

I have had a few of my actions recently get stuck like this. I will wait a bit then give it a kick and see if a retry works. AFAIK these all should be supported. Express 5 supports back to node 4 I think, maybe technically even the code works as far back as 0.10.

[wesleytodd]

Ah, it is not express or node support, it is the npm which shipped with node 14 which does not support the aliases. I think that was npm 6. I will try it again with a newer npm.

[wesleytodd]

Ok, I decided to just drop node 14 since this is targeting the 1.x we can take the technically breaking change of note testing in node@14 but the code should still run despite the tests not passing.

[wesleytodd]

Ok well since we got the test passing and I have an approval I will just go ahead and merge now. I will still leave that PR open until the morning.