Let me know and I will give it a try on my end.

I guess it could be something to do with my specific setup but it's just weird as we don't use yarn

Is

sst.json

at the repo root? And is the

yarn.lock

appearing also at the repo root after update?

Don't worry about it, Frank. I'll try removing yarn from my system entirely and see if that makes a difference. If others aren't seeing it, it's almost certainly peculiar to me

I tried putting a dummy

yarn.lock

at the parent diretory (1 level above

sst.json

)

I think the update command should only look within the current repo to decide if

yarn

or

npm

should be used.

Lemme cc @thdxr on this.

Next time when you update, let me know if you still see a

yarn.lock

generated even after removing the

yarn.lock

in the parent directory.