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
TypeScript errors starting with 15.4.2 #941
Comments
I'm seeing this as well. Seems related to DefinitelyTyped/DefinitelyTyped#62099 & DefinitelyTyped/DefinitelyTyped#62102 |
Same problem here while TS building. It should be just a matter of
Thanks for your hard work! |
Also requesting that this be bumped as the inclusion of this without allowing minor bumping in the lock causes depending on The upstream issue was fixed in |
Thanks, everyone. It's in v15.4.3. |
I use
release-it
for a number of packages (love it, btw, great work!), and have noticed that if I blindly update to the latest version (15.4.2
) I start getting TS errors:I also get this if I wipe out my
yarn.lock
file. meaning it is a nested dependency. Traversing throughyarn.lock
, I see that@types/cacheable-request
seem to be related togot
andupdate-notifier
, and sincegot
was updated in the most recent patch, I'm guessing that is the culprit.Naturally this is an upstream issue, but it is causing pain for consumers of your package. Is it possible that you can pin the version of
got
until the upstream issue is resolved? I do not get this error on15.4.1
, so my packages are pinned to this version for now.The text was updated successfully, but these errors were encountered: