Unexpected token import about es2017-lambda-boilerplate HOT 5 CLOSED

How are you running the code? Are you running it locally like this?

node src/index.js

A Lambda function isn't really meant to be run on your own local machine like this, since it's not a standalone application.

What I would recommend your workflow to be like is to do test-driven development (TDD), that is, write test cases as you are (or in fact, before) writing your function code. Then, run the tests using npm run build.

If you really want to just run the Lambda function on its own, you can use babel-node instead of node to run your code, but you also need to be calling the function from another file as well... Alternatively you can use npm run build to transpile down to ES5 before using node to call it.

from es2017-lambda-boilerplate.

My bad I was not up to date, it works with last version

from es2017-lambda-boilerplate.

No problem, did you mean latest version of the boilerplate, or Node?

from es2017-lambda-boilerplate.

Of the boilerplate ;)

from es2017-lambda-boilerplate.

Cool, thanks! :)

from es2017-lambda-boilerplate.