coderain blog

Fixing 'Cannot find module '/var/task/index'' AWS Lambda Error in Node.js Alexa Skill with OpenWeather API Integration

Building an Alexa Skill with AWS Lambda and external APIs like OpenWeather is a powerful way to create voice-enabled weather assistants. However, deploying such skills can sometimes hit roadblocks—one of the most common being the frustrating Cannot find module '/var/task/index' error. This error occurs when AWS Lambda fails to locate your skill’s entry point file (typically index.js), bringing your skill to a halt.

In this guide, we’ll demystify this error, explore its root causes, and walk through step-by-step solutions to fix it. We’ll also include context-specific examples for Node.js Alexa Skills integrated with the OpenWeather API, ensuring you can get your skill up and running smoothly.

2026-01

Table of Contents#

  1. Understanding the Error
  2. Common Causes of the Error
  3. Step-by-Step Fixes
  4. Testing the Fix
  5. Preventive Measures for Future Deployments
  6. Conclusion
  7. References

Understanding the Error#

The error message Cannot find module '/var/task/index' is Lambda’s way of saying: “I looked in the /var/task directory (where your code runs) for a file named index.js, but I couldn’t find it.”

  • /var/task: This is the default directory in AWS Lambda where your deployment package is unzipped and executed.
  • index: By default, Lambda expects the entry point file to be index.js unless explicitly configured otherwise.
  • Root Cause: The error almost always stems from issues with your project structure, deployment package, or Lambda handler configuration.

Common Causes of the Error#

Before diving into fixes, let’s identify why Lambda can’t find index.js:

  1. Incorrect Project Structure: index.js is not in the root of your project folder (e.g., nested in a subfolder like src/).
  2. Misconfigured Lambda Handler: The handler setting in Lambda (e.g., index.handler) points to a non-existent file or function.
  3. Malformed Deployment Package: The ZIP file uploaded to Lambda is missing index.js, or it’s zipped incorrectly (e.g., zipping the parent folder instead of its contents).
  4. Case Sensitivity Issues: Filenames like Index.js (uppercase “I”) won’t work on Lambda’s Linux-based environment, which is case-sensitive.
  5. ES Module (ESM) Misconfiguration: Using import/export (ESM) without setting "type": "module" in package.json, causing Node.js to fail parsing index.js.

Step-by-Step Fixes#

Let’s resolve the error with actionable steps, using a sample Alexa Skill project integrated with the OpenWeather API as context.

1. Verify Project Structure#

Your project must have index.js (the entry point) in the root directory. A typical structure for an Alexa Skill with OpenWeather API integration looks like this:

alexa-weather-skill/       # Project root  
├── index.js               # Lambda handler & skill logic  
├── package.json           # Dependencies (e.g., ask-sdk, axios)  
├── package-lock.json      # Dependency lock file  
└── node_modules/          # Installed dependencies (e.g., axios for OpenWeather API calls)

Why this matters: If index.js is nested in a subfolder (e.g., src/index.js), Lambda will not find it unless you explicitly update the handler path (e.g., src/index.handler). For simplicity, keep index.js in the root.

2. Check Lambda Handler Configuration#

Lambda uses the “Handler” setting to locate your skill’s entry function. By default, this is set to index.handler, which means:

  • index: The filename (index.js).
  • handler: The exported function in index.js (e.g., module.exports.handler = ...).

How to verify:

  1. Go to the AWS Lambda Console and select your function.
  2. Under “Configuration” > “General configuration,” check the “Handler” field.

Example: For an OpenWeather-integrated skill, your index.js might look like this (simplified):

const Alexa = require('ask-sdk-core');  
const axios = require('axios'); // For OpenWeather API calls  
 
const OpenWeatherApiKey = 'YOUR_API_KEY';  
const OpenWeatherBaseUrl = 'https://api.openweathermap.org/data/2.5/weather';  
 
const GetWeatherIntentHandler = {  
  canHandle(handlerInput) {  
    return Alexa.getRequestType(handlerInput.requestEnvelope) === 'IntentRequest'  
      && Alexa.getIntentName(handlerInput.requestEnvelope) === 'GetWeatherIntent';  
  },  
  async handle(handlerInput) {  
    const city = Alexa.getSlotValue(handlerInput.requestEnvelope, 'City');  
    const weatherData = await axios.get(`${OpenWeatherBaseUrl}?q=${city}&appid=${OpenWeatherApiKey}&units=metric`);  
    const temp = weatherData.data.main.temp;  
 
    return handlerInput.responseBuilder  
      .speak(`The current temperature in ${city} is ${temp} degrees Celsius.`)  
      .getResponse();  
  }  
};  
 
exports.handler = Alexa.SkillBuilders.custom()  
  .addRequestHandlers(GetWeatherIntentHandler)  
  .lambda();

Here, the handler is exported as exports.handler, so the Lambda Handler setting should be index.handler.

3. Create a Correct Deployment Package#

Lambda requires a ZIP file containing index.js, package.json, and node_modules. If the ZIP is malformed (e.g., missing files or zipping the parent folder), Lambda won’t find index.js.

Steps to create a valid ZIP:

Step 3.1: Install Dependencies#

Ensure node_modules is present by installing dependencies. Run this in your project root:

npm install ask-sdk-core axios --save

This installs the Alexa Skills Kit (ASK) SDK and axios (for OpenWeather API calls).

Step 3.2: Zip the Root Directory Contents#

Zip only the files in the project root (not the parent folder).

  • Windows (PowerShell):

    Compress-Archive -Path * -DestinationPath lambda-deploy.zip -Force

  • Mac/Linux (Terminal):

    zip -r lambda-deploy.zip . -x "*.git*" "*.env*"  # Exclude .git, .env, etc.

Critical: If you zip the parent folder (e.g., alexa-weather-skill.zip containing the alexa-weather-skill/ folder), Lambda will unzip to /var/task/alexa-weather-skill/, and /var/task/index.js will not exist.

4. Ensure Filename Case Sensitivity#

Lambda runs on Amazon Linux, which is case-sensitive. If your file is named Index.js (uppercase “I”) instead of index.js, Lambda will fail to find it.

Fix: Rename the file to index.js (lowercase) and update the handler in Lambda if needed (though index.handler will work with index.js).

5. Fix ES Module (ESM) Compatibility Issues#

If you’re using ESM syntax (import/export instead of require/module.exports), Node.js requires "type": "module" in package.json to parse index.js correctly.

Example package.json for ESM:

{  
  "name": "alexa-weather-skill",  
  "version": "1.0.0",  
  "type": "module",  // Add this line for ESM  
  "dependencies": {  
    "ask-sdk-core": "^2.14.0",  
    "axios": "^1.6.0"  
  }  
}

Handler Export for ESM:
In index.js, use export const handler = ... instead of module.exports.handler:

import Alexa from 'ask-sdk-core';  
import axios from 'axios';  
 
// ... (same weather logic as before)  
 
export const handler = Alexa.SkillBuilders.custom()  
  .addRequestHandlers(GetWeatherIntentHandler)  
  .lambda();

Lambda Handler Setting: For ESM, the handler remains index.handler (Lambda supports ESM in Node.js 14+ runtimes).

Testing the Fix#

After applying the fixes, deploy the updated ZIP to Lambda and test:

  1. Re-deploy the ZIP: In the Lambda Console, under “Code” > “Deployment package,” upload lambda-deploy.zip.
  2. Check CloudWatch Logs: Go to “Monitor” > “Logs” to view Lambda execution logs. If successful, you’ll see entries like START RequestId: ... without Cannot find module errors.
  3. Test the Alexa Skill: Use the Alexa Developer Console to test your skill. Trigger the GetWeatherIntent (e.g., “Alexa, ask My Weather Skill for the weather in London”)—it should return temperature data from OpenWeather.

Preventive Measures for Future Deployments#

To avoid this error in future projects:

  • Use a Consistent Structure: Always keep index.js in the project root.
  • Automate Deployment: Use tools like AWS SAM, Serverless Framework, or the ASK CLI to auto-generate deployment packages. For example, the ASK CLI runs ask deploy to zip and upload code to Lambda.
  • Lint Filenames: Ensure filenames are lowercase (e.g., index.js) and avoid spaces/special characters.
  • Validate Dependencies: Run npm install before zipping to ensure node_modules is up-to-date.
  • Test Locally: Use ask simulate (ASK CLI) or lambda-local to test your skill locally before deploying.

Conclusion#

The Cannot find module '/var/task/index' error in AWS Lambda is almost always due to misconfigured project structure, deployment packages, or handler settings. By ensuring index.js is in the root directory, zipping the correct files, and verifying the handler configuration, you can resolve this issue quickly.

With these fixes, your Alexa Skill will successfully run on Lambda and integrate with the OpenWeather API, delivering real-time weather updates to users.

References#