Hi guys, after the migration to SST 1.x (1.1.1) I am getting the following warnings on the screen and they are quite annoying, one of the solutions could be to apply a null coalescence, but I don’t want to mess up my code, any recommendations? (I’m using plain javascript)

I'm actually planning on making an update to surpress this exact warning

That’s good news, I also get another strange warning while building the api routes using the spread operator (as shown in the image), the final generated object is the correct one, therefore I cannot understand the warning message

Hm ok we need to think about this one

No problem, of course I can test it, but you know that the sst update command doesn’t work either, some time ago I was going to report an issue on github and I never did. My current project is inside a monorepo and for some reason the sst update does not modify the package.json of the project, therefore I always do manual updates

ah yeah it's a bit hard for us to keep up with all the different package managers / setups

hahaha, I reported many things to you together, sorry for that 🤭

can just update package.json to that version

0.0.0-20220518184941 ?

cli resources and core

for some reason i never got the core package 🤔

ah core isn't a subdependency you don't need to explicitly add it

great, and what should I check in this pre release build?

Hey @outaTiME after u update, you shouldn’t be getting the error

Type "undefined" is not assigned to type "string"

.

thanks @Frank, I no longer have warnings of

Type "undefined" is not assigned to type "string"

on version 1.1.2 🙌