New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARNING: Plugin ServerlessWebpack uses deprecated hook before:deploy:createDeploymentArtifact #126

Closed
alfonsoperez opened this Issue May 22, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@alfonsoperez
Copy link

alfonsoperez commented May 22, 2017

Getting these warnings while deploying my functions:

Serverless: WARNING: Plugin ServerlessWebpack uses deprecated hook before:deploy:createDeploymentArtifacts
Serverless: WARNING: Plugin ServerlessWebpack uses deprecated hook after:deploy:createDeploymentArtifacts

Serverless version: 1.13.1
Serverless-webpack version: ^1.0.0-rc.4

@HyperBrain

This comment has been minimized.

Copy link
Member

HyperBrain commented Jun 28, 2017

The plugin should hook the new aws:package:* events instead.

For a detailed overview see the lifecycle cheat sheet

@HyperBrain

This comment has been minimized.

Copy link
Member

HyperBrain commented Sep 22, 2017

This is a breaking change according to semver as it will require a Serverless version of 1.12+ and will leave users of previous Serverless versions behind.

So I'll remove the 3.1.0 milestone and add it to a breaking 4.0.0 milestone.

@HyperBrain HyperBrain modified the milestones: 3.1.0, 4.0.0 Sep 22, 2017

@HyperBrain HyperBrain referenced this issue Sep 28, 2017

Merged

Hook to package:createDeploymentArtifacts #244

3 of 7 tasks complete
@akolybelnikov

This comment has been minimized.

Copy link

akolybelnikov commented Oct 22, 2017

@HyperBrain how can I make the plugin hook the new aws📦* events?
Serverless Version: 1.23.0
Serverless-webpack version : ^3.1.2

@HyperBrain

This comment has been minimized.

Copy link
Member

HyperBrain commented Oct 23, 2017

@akolybelnikov This is fixed in #244 . I will prepare a release in the next days, so the warnings are gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment