"No matching handler found" when handlers aren't in the root folder

This is a (Bug Report)

Since the version 2.2 and this PR my config is broken.

Description

When the lambda handlers aren’t in the root folder (this.serverless.config.servicePath) serverless-webpack doesn’t find them.

$ serverless deploy Serverless Error --------------------------------------- No matching handler found for ‘TestHandler’. Check your service definition.

Reading the code, I understand that the plugin is looking for the files in the root folder, but in my project, neither the original typecript files nor the transpired files are there.

const files = glob.sync(`${fileName}.*`, {
        cwd: this.serverless.config.servicePath,
        nodir: true
      });

The hierarchy:

-app
  - handlers/ (all the lambda handlers)
-dist (webpack output path)
-serverless.yml
-webpack.config.js
-package.json

Additional Data

I initialized a test repo to show the behavior: https://github.com/jerep6/serverless-webpack-issue

• Serverless-Webpack Version you’re using: 2.2.2
• Webpack version you’re using: 3.3.5
• Serverless Framework Version you’re using: 1.19.0
• Operating System: MacOS

[HyperBrain]

Thanks for creating the issue 👍 .This is because your handler definition in your serverless.yml seems to not match your handler locations. In Serverless, function handlers have to point to their respective locations if located in subdirectories (at least for AWS and OpenWhisk) - only Google is different as they do not have a file-based handler concept.

serverless-webpack since version 2.2 enforces that the definitions are correct.

Can you please check if your handler definitions in serverless.yml are correct? I.e. if your handler file is somewhere in <service_dir>/src/handlers/myhandler.js the handler definition in the yaml file must be src/handlers/myhandler.myfunc.

[HyperBrain]

Closing the issue as you found a solution 😃