You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By mistake, I have updated some of the files (it was typescript), and after some bug fixing related to that, I have noticed that you are missing a lot of @types and most of them are obsolete!
for example:
currently installed
some of them don't have super changes but other like sinon / mocha are quite obsolete
+ you in one package i have noticed you don't use @types for jest (it can cause some type error in the future)
The text was updated successfully, but these errors were encountered:
With regards to TypeScript 3.5, I'm waiting for the fix for microsoft/TypeScript#31676 to be released (will hopefully be 3.5.2). After that I we will be able to update TypeScript itself.
With regards to the @types dependencies, they're not exactly "obsolete". We're using dependabot to automagically update our dependencies. The thing is, it will only create a PR if the new version is outside of the semver range. For example "@types/lodash": "^4.14.134", is still in ranche of "@types/lodash": "^4.14.110", and so it will not create a PR for it. We're also happy with not following patch releases as it would create a lot of PR's.
I would agree that we should never use ^, instead use ~. That way we will get a PR for minor releases.
The only one that is really outdated are mocha and sinon. Updating sinon will be a lot fo work because of this issue: DefinitelyTyped/DefinitelyTyped#36019. I'm not sure why mocha isn't updated.
By mistake, I have updated some of the files (it was typescript), and after some bug fixing related to that, I have noticed that you are missing a lot of @types and most of them are obsolete!
for example:
currently installed
current:
some of them don't have super changes but other like sinon / mocha are quite obsolete
+ you in one package i have noticed you don't use @types for jest (it can cause some type error in the future)
The text was updated successfully, but these errors were encountered: