Regression > 0.1.7 about path-to-regexp HOT 4 CLOSED

This not a regression or a bug, the documentation is in the README. If you want the literal translation between old and new formats it's /files/:file(.*) and (.*) (* basically means .* in 0.1.x), feel free to open a PR to add them to the compatibility docs if you think it'd help others!

from path-to-regexp.

@blakeembrey sorry that i ping you again but i tested it and i still get

pathToRegexp get called with {
  path: '.*',
  opts: { sensitive: undefined, strict: undefined, end: true },
  keys: []
}

TypeError: Unexpected MODIFIER at 1, expected END

maybe i need to explicit do /(.*)
?

from path-to-regexp.

Ok i got it all works nice thanks a lot for the good documentation do you know any reason for express to not take the new syntax?

from path-to-regexp.

for express to not take the new syntax?

The current express router is still based on the old version, when it upgrades it'll get the new syntax (in express 5).

from path-to-regexp.