-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SxS issue with @pulumi/pulumi
introduced in 1.7.0
#3652
Comments
Marking P1 until we identify how broad of an issue this is. Several reports of this in the first 24 hours |
Users who saw this indicated that blowing away |
Not sure if this is related but I had this issue today:
Same code with tsc 3.4.1 works fine, after an update to tsc 3.7.3 this issue happens. I confirm that after deleting package-lock.json and node_modules it works. |
i'll look into this. it sounds like tsc might have gotten stricter and something we do in our typings makes it unhappy. I've also seen something similar in a downstream lib. This line is pretty interesting:
I think something is getting inferred as -- This doesn't seem super high pri though given that it is fixable by unlocking things. |
I have figured this out. An unfortunate confluence of a change i made and TS 3.7 getting stricter. Will fix asap. |
Fixed with #3658. Will be trying to get this out asap to a 1.7.1 release. |
We have seen a couple reports of issues when users have
1.7.0
sxs with earlier versions (like1.6.1
). This can lead to incompatibilities betweenOutput<T>
in the newer and older libraries. Feels like this is most likely related to this change.The text was updated successfully, but these errors were encountered: