Catch-all routes aren't parsed properly

Describe the bug Using a catch-all route with format [[...paramName]].tsx leads to a path-to-regexp error when deploying

To Reproduce

1. Using a Next.js project set-up with a minimal serverless.yml file (as per the README), add a file named [[...template]].tsx under pages. A minimal Next.js page can be used for the content.
2. Attempt deploy (serverless)
3. See error in console

Expected behavior Deployment should occur without issues. This is the case for me when I rename [[...paramName]].tsx to [...paramName].tsx. Furthermore, debugging shows that this is the route that is causing issues.

Screenshots If applicable, add screenshots to help explain your problem.

TypeError: Missing parameter name at 12

Desktop (please complete the following information):

• OS: macOS Catalina 10.15.1
• Version @sls-next/serverless-component@1.16.0-alpha.0

[kulesa]

As a workaround for optional catch-all routes, instead of, say, pages/posts/[[...params]].js you can create pages/posts/index.js and pages/posts/[...params].js where [...params].js is just

export { default } from '.'

Now /posts route will render index.js with router.query === {}, and /posts/published/recent will also render index.js but with router.query.params === ['published', 'recent'].

[ivanpetrushev]

That warning has disappeared from docs, so maybe Optional catch all routes now should be supported? I am getting the same error.