configure sam build --watch support about aws-sam-webpack-plugin HOT 5 OPEN

@asankagit Are you saying that changes to the functions aren't appearing or that changes to your SAM project aren't appearing?

from aws-sam-webpack-plugin.

yes I have configured my webpack.config.js and package.js as above

from aws-sam-webpack-plugin.

@asankagit
Maybe you can achieve this by using two terminals.

## 1st terminal
npm run build
## 2nd terminal
sam local start-api

from aws-sam-webpack-plugin.

@asankagit
One solution could be to use something like concurrently like I've used on my boilerplate

The reason for the initial npm run build is to ensure the container doesn't start up with old files or an empty directory.

from aws-sam-webpack-plugin.

Webpack watch does seem to work for me. The slowness makes it hard to tell if latest changes are completed or still a in progress. Sometimes I could see a build complete just as I get ready to run, but it was actually a previous build that had not finished but did not have latest changes.

I found it more efficient to manually run the build than keep wondering if I needed to wait longer for the "latest" change.

from aws-sam-webpack-plugin.