Features

• The plugin will now properly pull in config from an iopipe entry in package.json or an iopipe.rc file
• Do not wepback dependencies, move them into dependencies in package.json

Chores

• Update docs to recommend $IOPIPE_TOKEN usage
• Update docs with FAQ area
• New test projects

Breaking Changes

• None

Hooray! The team at IOpipe has loved seeing the validation for this project, and we hope to continue to improve upon development workflows for serverless architectures.
We feel that this project has stabilized to a 1.0.0 point. Enjoy!

Breaking Changes

• None

Bugfixes

• Does not warn when using extra flavors of the IOpipe agent library including the recommended @iopipe/iopipe

Bug Fixes

• Previous functionality slightly discouraged use of environment variables implicitly. This has now been corrected. You will receive a warning if iopipeToken is not found in the serverless.yml custom section, but it will not actively error out.
• Support YAML interpolation. Due to the structure of the code previously, interpolated values in the serverless.yml such as IOPIPE_TOKEN: ${env:IOPIPE_TOKEN} were improperly handled. This has been corrected.

Chores

• Rename example folder to testProject (as it is used for unit tests)
• Add actual example!

Breaking Changes

• None

Fixes a bug where the plugin erroneously relied on a certain user project folder structure.

Bug Fixes

• Auto-upgrade functionality failed if the user's source package.json threw warnings (missing license etc).

• Fixes #26
• See #27

• Webpack for a small, compiled file. Decreases upload size to cloud provider!
• Display errors better in the cli or console by using try/catch
• Use Prettier for formatting

• Fixes bug where engines mismatched babel support option
• Support Node 4.2.6

Major Change!

One of the original goals of the plugin was to keep the file and handlers that AWS executes after package deploy the same when using this plugin. In order to do that, we chose to pursue a strategy of running handlers through an AST transform. While this was 🆒 in some ways, it was un-🆒 in others. Namely, the plugin was best installed globally and linked with npm link. This made the plugin more difficult to install and maintain.

So, we decided to drop the requirement of keeping the original file/handler. With this requirement gone, we can pursue a much simpler path of generating a single file that uses require to import the handlers and run them in-place.

There are technically no breaking changes for this release, other than the install method, which we now suggest npm install serverless-plugin-iopipe vs a global install. The plugin is much lighter weight and will not bloat your package size nearly as much.

Fixes an issue where plugin would fail on dependency checks.