https://serverless-stack.com/ logo
Join Slack
Powered by
excellent! :tada: any progress on getting `sst up...
# general
s
excellent! 🎉 any progress on getting 
sst update
working with Yarn 2.x/3.x? it still does nothing
r
I'm getting a yarn.lock appear in the project root when I run 
npx sst update
which is odd because I don't use yarn...
Going from 0.50.2 => 0.50.3
Also start of build log mentions a debugger listening when running deploy which I've never noticed before, is that correct?
Copy code
> wheresmytech@1.1.132 deploy:eon-test
> AWS_PROFILE=eon sst deploy --stage eon-test

Using stage: eon-test
Preparing your SST app
Detected tsconfig.json
Transpiling source
Running type checker
Debugger listening on <ws://127.0.0.1:57439/a2d6a8cf-4dab-4cfc-989e-ca44869b312b>
ö
As far as I know, the default packager is 
yarn
, you might need to pass additional 
--use-npm
f
@Ross Coundon Let me loop in @thdxr for the two issues.
t
@Ross Coundon is there a yarn.lock in any of the parent directories? That's how we figure out if it's a yarn project or not
The Debugger line is weird, I'm not seeing that
I'll look into that tomorrow
r
No problem, there are 3 packages in node_modules that have a yarn.lock but that's all.
It even appears when running
Copy code
sst update --use-npm
Although I don't see that as a command line option but thought I'd try The yarn.lock file seems to be written when the 2nd line is printed
Copy code
Updating @serverless-stack/cli to latest
Updating @serverless-stack/resources to latest
I think the debugger thing is unrelated to SST, I'm seeing it spring up when running Jest too, so I think it's maybe a VSC update related thing, or maybe a plugin related thing
Open in Slack
PreviousNext
Powered by