serverless-webpack 5.5.0 attempts to run Webpack on container images which are not JavaScript

This is a Bug Report

Description

For bug reports:

• What went wrong?

serverless-webpack is stopping me from deploying lambda containers as part of my service that are not

• What did you expect should have happened?

it should not have touched them as they’re not relevant to webpack

• What was the config you used?

N/A

I assume this is related to https://github.com/serverless-heaven/serverless-webpack/pull/723, which I can see the sense in - however, I can’t see a way to say “this isn’t a container image that Webpack cares about” and hence ignore that lambda in the service definition. Ideally there’d be an option to opt in/out of either Webpack’s involvement in particular functions, or container functions as a whole as not all container functions are guaranteed to be part of the service.

Additional Data

$ /Users/chris/Code/report-support/node_modules/.bin/serverless deploy -v --stage dev
Serverless: Using configuration:
{
  "webpackConfig": "api/webpack.config.js",
  "includeModules": {
    "forceInclude": [
      "pg"
    ]
  },
  "packager": "yarn",
  "keepOutputDirectory": true,
  "packagerOptions": {},
  "concurrency": 12
}
 
 Serverless Error ----------------------------------------
 
  No matching handler found for 'apollo' in 'XXX'. Check your service definition.
 
  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com
 
  Your Environment Information ---------------------------
     Operating System:          darwin
     Node Version:              14.16.1
     Framework Version:         2.41.1 (local)
     Plugin Version:            4.6.0
     SDK Version:               4.2.2
     Components Version:        3.9.2

[cnorthwood]

with apologies, it looks like I failed to change to the right branch - yes, that appears to be correct now

[cnorthwood]

in the definition of the server function, I would assume it’s looking at the command of the lambda