Fail early if lambda source isn't available about aws-sam-webpack-plugin HOT 6 CLOSED

@vadzim Can you provide an example of this?

from aws-sam-webpack-plugin.

Oh.. I thought it's by design..
Ok, I'll try to extract minimal example

from aws-sam-webpack-plugin.

https://github.com/vadzim/AwsSamTestData

template.yaml contains a reference to non-existing file Z.js

actions:

• run npm run build

actual behaviour:

• command runs successfully and show neither erros nor warnings. It builds one lambda function which has a valid reference to X.js

expected behaviour:

• command shows some info about wrong entry in template.yaml

In the first commit vadzim/AwsSamTestData@21e78b8 template.yaml contains two valid references to X.js and Y.js and build them both successfully.

from aws-sam-webpack-plugin.

Here https://github.com/SnappyTutorials/aws-sam-webpack-plugin/blob/570602bebf8d25777dec647c551175ed5c8bec8f/src/index.ts#L97 the code checks if the file with extension .js or .ts exists and creates an entry for webpack only if that file exists. The code just does nothing if the file does not exist. It neither adds some entry nor reports any error.

from aws-sam-webpack-plugin.

Webpack allows to specify entries without extensions and also specify an option how to resolve files without extensions:

  entry: {
    X: './src/X',
    Y: './src/Y',
  },
  resolve: {
    extensions: ['.ts', '.js'],
  },

I guess to solve the problem it could be enough to just generate entry without either .ts or .js extension, remove any checks for the existing files and let webpack do its work.
In such case webpack will be responsive for error handling if entry is absent.

There is an example which checks that webpack can handle entries without extensions https://github.com/vadzim/AwsSamTestData/tree/WebpackEntryWithoutExtension

from aws-sam-webpack-plugin.

Great work @vadzim

from aws-sam-webpack-plugin.