Jovo update moves dev dependencies into prod dependencies

cli
#1

Hi jovo!

I have the jovo-cli package 3.0.14 configured as dev dependency in my package.json.
I need there to run the VSC Debgugger feature.

When i do a jovo update the command line asks me if i want to upgrade these packages:

jovo-cli: 3.0.14 -> 3.0.15
jovo-cli-core: 3.0.3 -> 3.0.4
jovo-cli-deploy-lambda: 3.0.3 -> 3.0.4
jovo-cli-platform-alexa: 3.0.9 -> 3.0.10
jovo-cli-platform-google: 3.0.6 -> 3.0.7

I hit yes and the magic begins.

After updating i end up with the jovo-cli still in the dev dependencies, but now i have these packages in my production dependencies:

"jovo-cli-core": "^3.0.4",
"jovo-cli-deploy-lambda": "^3.0.4",
"jovo-cli-platform-alexa": "^3.0.10",
"jovo-cli-platform-google": "^3.0.7",

This increases package size without any benefit.

Best,
Dominik.

#2

Good catch, thank you. We will fix it.

#3

Hi @AlexSwe, sorry to say: It still persists in jovo-cli: 3.0.18.

jovo update

jovo-cli: 3.0.18 -> 3.0.20
jovo-cli-core: 3.0.4 -> 3.0.5
jovo-cli-deploy-lambda: 3.0.4 -> 3.0.5
jovo-cli-platform-alexa: 3.0.11 -> 3.0.12
jovo-cli-platform-google: 3.0.7 -> 3.0.8

and now i have

“jovo-cli-core”: “^3.0.5”,
“jovo-cli-deploy-lambda”: “^3.0.5”,
“jovo-cli-platform-alexa”: “^3.0.12”,
“jovo-cli-platform-google”: “^3.0.8”,

in my prod-dependencys

Thanks for fixing!

#4

Will look into it, thank you.

#5

Fixed :slight_smile:

#6

jovo-cli: 3.0.20 still moved from dev to prod :frowning:

#7

Weird, will check. Thanks

#8

Could you try again with 3.0.21? And make sure the local Jovo CLI has this version too?