https://serverless-stack.com/ logo
Join Slack
Powered by
awesome work as usual! :trophy:
# general
s
awesome work as usual! šŸ†
a
What about the 
update
command? is not used anymore?
j
@AdriƔn Mouly what do you mean?
a
Previous release you guys added the update command.
But in the release notes doesnā€™t say to use that to update.
Its saying to use NPMā€¦. and I use yarn, for example.
The update command is supposed to cover that?
j
Ah in the release notes. Yeah Yarn works, npm works, and the update command also works. We were just documenting npm because it was more common. It gives me an idea though. @thdxr how about if the update command took a specific SST version. Then maybe we could start using that in our release notes.
a
Iā€™ve tried running update, but nothing happened.
I mean, 0 packages updated.
t
@Jay yeah was thinking along the same lines I can do that. @AdriƔn Mouly you're running 
yarn sst update
?
a
I have this on my package.json:
ā€œupdateā€: ā€œsst updateā€,
t
can you try running 
yarn sst -v update
and see the output
a
Well maybe something got updated.
But no updates on my packge.json?
My json still has:
Copy code
"@serverless-stack/cli": "0.40.0",
    "@serverless-stack/resources": "0.40.0",
This is the beginning of the log, but there is a bunch of warnings.
t
hm ok what does it say when you don't have the 
-v
can you share your full package.json as well
a
This is withtout -v.
Copy code
{
  "name": "mycomp-serverless",
  "version": "0.1.0",
  "private": true,
  "workspaces": [
    "frontend",
    "src/packages/*",
    "src/services/*"
  ],
  "scripts": {
    "test": "sst test",
    "update": "sst update",
    "start:local": "AWS_PROFILE=development sst start --stage $USER",
    "build:local": "AWS_PROFILE=development sst build --stage $USER --verbose",
    "deploy:local": "AWS_PROFILE=development sst deploy --stage $USER",
    "remove:local": "AWS_PROFILE=development sst remove --stage $USER"
  },
  "devDependencies": {
    "@aws-cdk/assert": "1.114.0",
    "@types/aws-lambda": "^8.10.70",
    "@types/node": "^14.14.31",
    "lerna": "^3.22.1"
  },
  "dependencies": {
    "@aws-cdk/core": "1.114.0",
    "@serverless-stack/cli": "0.40.0",
    "@serverless-stack/resources": "0.40.0",
    "@types/node": "^14.14.31",
    "aws-sdk": "^2.957.0"
  }
}
t
There were some bug fixes to the update command in 0.40.1
can you manually update to latest and run the command again?
a
Ok sure.
t
Think there was a bug in 0.40.0 where if the deps are not in devDependencies you'd see that error
a
Where should it be?
SST should be dev or not dev?
t
Depends on your point of view haha. We just had a bug with one
a
Ok.
t
I personally put it in dev but I never really had clarity on the differences
a
Yeah due this is a tool, might be fine dev.
Update this 2?
ā€œ@serverless-stack/cliā€: ā€œ0.40.1",
ā€œ@serverless-stack/resourcesā€: ā€œ0.40.1",
Nothing else?
Worked now, after updating to 0.40.1
`
Copy code
> yabble-serverless@0.1.0 update
> sst update

Updating @serverless-stack/cli
Updating @serverless-stack/resources
Updating @aws-cdk/core@1.114.0
Updating @aws-cdk/assert@1.114.0
SST: 0.40.2
CDK: 1.114.0
Thanks guys.
j
Glad we sorted it out!
t
Cool, made an issue to update to a specific version so in the future we can say in release notes use 
sst update 0.40.2
to update
j
Yeah I like it. Cos it covers updating all the CDK packages. The current one in the release notes only does a part of it.
3 Views
Open in Slack
PreviousNext
Powered by