serverless-bundle
serverless-bundle copied to clipboard
Deprecation warning: CLI options definitions were upgraded with "type" property
Getting deprecation warning while running the sls deploy command line.
Serverless: Deprecation warning: CLI options definitions were upgraded with "type" property (which could be one of "string", "boolean", "multiple"). Below listed plugins do not predefine type for introduced options: - ServerlessPlugin for "out" Please report this issue in plugin issue tracker. Starting with next major release, this will be communicated with a thrown error. More Info: https://www.serverless.com/framework/docs/deprecations/#CLI_OPTIONS_SCHEMA
Same here. Versions are as follows:
$ serverless --version
Framework Core: 2.34.0
Plugin: 4.5.3
SDK: 4.2.2
Components: 3.8.2
and for serverless-bundle it's 3.2.1
Also having this issue.
Serverless: Deprecation warning: CLI options definitions were upgraded with "type" property (which could be one of "string", "boolean", "multiple"). Below listed plugins do not predefine type for introduced options: - ServerlessWebpack for "out" Please report this issue in plugin issue tracker. Starting with next major release, this will be communicated with a thrown error. More Info: https://www.serverless.com/framework/docs/deprecations/#CLI_OPTIONS_SCHEMA
$serverless --version Framework Core: 2.35.0 Plugin: 4.5.3 SDK: 4.2.2 Components: 3.8.3
"serverless-webpack": "^5.4.1", "webpack-node-externals": "^2.5.2"
It is this plugin that causes it, but I have the latest version of this plugin... **plugins:
- serverless-webpack**
There is a fix for this on the master branch of the serverless-webpack plugin (which ServerlessPlugin extends).
https://github.com/serverless-heaven/serverless-webpack/pull/774
Looks to be in the 5.4.2 release milestones
https://github.com/serverless-heaven/serverless-webpack/milestone/36?closed=1
Now that serverless-webpack version 5.4.2 has been released, is it possible for serverless-bundle to include the equivalent fix so that the ServerlessPlugin for "out" warning from the initial comment is resolved too?