Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

TypeError: Missing parameter name at 13

See original GitHub issue

Serverless.yml:

  component: '@sls-next/serverless-component@1.19.0-alpha.2'

I’m using nextjs 10. When I run npx serverless I get the following error:

TypeError: Missing parameter name at 13
    at lexer (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/path-to-regexp/dist/index.js:48:23)
    at parse (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/path-to-regexp/dist/index.js:98:18)
    at stringToRegexp (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/path-to-regexp/dist/index.js:331:27)
    at Object.pathToRegexp (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/path-to-regexp/dist/index.js:405:12)
    at Object.exports.default (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/@sls-next/lambda-at-edge/dist/lib/pathToRegexStr.js:4:46)
    at Object.entries.forEach (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/@sls-next/lambda-at-edge/dist/build.js:282:56)
    at Array.forEach (<anonymous>)
    at Builder.<anonymous> (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/@sls-next/lambda-at-edge/dist/build.js:251:43)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/me/.serverless/components/registry/npm/@sls-next/serverless-component@1.19.0-alpha.2/node_modules/@sls-next/lambda-at-edge/dist/build.js:5:58)

Is someone able to point me in the right direction? Thanks!

Issue Analytics

State:
Created 3 years ago
Comments:5

Top GitHub Comments

2reactions

dphangcommented, Nov 7, 2020

Ok, I think it is your optional catch-all pages/app/profile/[[...slug]].js which is not parsed properly. You can try the workaround here for now: https://github.com/serverless-nextjs/serverless-next.js/issues/523.

We will take a look at how to properly support this for 1.19.

0reactions

dphangcommented, Nov 11, 2020

Cool, I’ll close this and track it in the related issue. Thanks!

Top Results From Across the Web

TypeError: Missing parameter name at 14 - Stack Overflow

I am building a simple server on Javascript using node.js platform. I have 2 files which are called server.js and db.js.

Framework7-bundle.min.js:13 Uncaught TypeError

When i try to navigate to another page, i got this error on console : framework7-bundle.min.js:13 Uncaught TypeError: Missing parameter name ...

SyntaxError: missing formal parameter - JavaScript | MDN

The JavaScript exception "missing formal parameter" occurs when your function declaration is missing valid parameters.

SQL error messages and exceptions - Oracle Help Center

Parameter <parameterName> is an <procedureName> procedure parameter and must be registered with CallableStatement.registerOutParameter before execution. 07009 ...

Type Errors - Pyre

This line will raise at runtime, but no type error here since `f()` has type `Any`. ... Pyre produces an Unbound Name error...