Typescript/ESLint error: Unable to resolve path to module 'aws-lambda' import/no-unresolved

Question

I have a serverless project written with typescript. When I run ESLint I am getting the following error:

  1:85  error  Unable to resolve path to module 'aws-lambda'  import/no-unresolved

For the following line of code: import { APIGatewayProxyEvent, APIGatewayProxyHandler, APIGatewayProxyResult } from 'aws-lambda'; (I have "@types/aws-lambda": "^8.10.64" in my devDependencies).

I don't understand what could be the error, as the typing is installed and if I try to import from "@types/aws-lambda" VS Code tells me to import from "aws-lambda" directly.

What am i doing wrong here please?

My webpack.config.js looks like this - github.com/serverless-heaven/serverless-webpack/blob/master/… — Pablo
– Pablo, Commented Dec 19, 2020 at 12:50
Unfortunately it did not help. I have added all my files to this public gist: gist.github.com/gomesp/… — Pablo
– Pablo, Commented Dec 20, 2020 at 1:04

Marty ZHANG · Accepted Answer · 2021-08-05 06:04:37Z

6

hendrixchord's anwser helped me to resolve the issue, but here is the trimmed down version of the necessary steps that really worked for me:

# It's a must, otherwise the below `settings` won't work:
$ npm install --save-dev eslint-import-resolver-typescript
# Not `--save-dev`.
$ npm install @types/aws-lambda

In the .eslintrc file (note that I'm using the .js version):

  settings: {
    'import/resolver': {
      typescript: {
        alwaysTryTypes: true,
      },
    },
  },

edited Aug 5, 2021 at 6:04

answered Aug 5, 2021 at 5:44

Marty ZHANG

3423 silver badges9 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

goerlitz Over a year ago

This seems to be the relevant issue: github.com/import-js/eslint-plugin-import/issues/1485 Still, I don't understand why @types/aws-lambda should not be placed in devDependencies. Any good reason for that?

hendrixchord · Accepted Answer · 2020-12-20 12:16:02Z

This is the config in my .eslintrc file

   "settings": {
        "import/parsers": {
            "@typescript-eslint/parser": [".ts", ".tsx"]
        },
        "import/resolver": {
            "typescript": {
                "alwaysTryTypes": true,
                "paths": "./tsconfig.json",
            },
        }
    },

Also I've noticed in your tsconfig.json file you've not included typeRoots since you've excluded node_modules in your exclude property. It should be like this

    "typeRoots": [
        "./node_modules/@types"
    ],
    "exclude": [
        "/node_modules/",
        ".serverless/**/*",
        ".webpack/**/*",
        "_warmup/**/*",
        "vscode/**/*",
        "lib/**/*",
        "tests"
    ]

If all of that fails the last resort would be to add it to the ignore list in .eslintrc file.

    "import/no-unresolved": [
        "error",
        {
            "ignore": [
                "aws-lambda"
            ]
        }
    ],

arpadt · Accepted Answer · 2021-02-23 07:07:10Z

3

If I use AWSLambda.APIGatewayProxyEvent when I define the type, it works for me:

const event: AWSLambda.APIGatewayProxyEvent = ...

I didn't have to modify anything.

answered Feb 23, 2021 at 7:07

arpadt

1098 bronze badges

Collectives™ on Stack Overflow

Typescript/ESLint error: Unable to resolve path to module 'aws-lambda' import/no-unresolved

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related