Typesync adding old alpha versions of types.
See original GitHub issueFor instance, when I had a dependency of "bcrypt": "^3.0.7"
- it gave me "@types/bcrypt": "^10.0.28-alpha"
which is 3 years old. The latest version of @types/bcrypt
is actually 3.0.0
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
jeffijoe/typesync: Install missing TypeScript typings for ... - GitHub
TypeSync will add typings for packages that: have a @types/package available; don't already provide typings internally (the typings and types field in ...
Read more >How can I find previous version of NPM @types - Stack Overflow
On the NPM site I have searched for AngularJs and found version 1.5.14 alpha. How can I get a list of all versions...
Read more >typesync - npm
Start using typesync in your project by running `npm i typesync`. ... TypeScript icon, indicating that this package has built-in type ...
Read more >Making a Poison-type Sync Pair every now and then until I get ...
She tried to kill Ash like 3 times, 2 of those with Drapion and Salamence, was efficient af, and is the 1st Pokémon...
Read more >If you have just changed code (for example deployed ... - Drupal
I got the following error: Exception: The configuration directory type 'sync' does not exist in config_get_config_directory() ( ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@genesiscz
I believe the reason for the issue is because the maintainers of the types for
react-scroll
neglected to mark the version you specified -3.0.27
- with the-alpha
suffix. Typesync thus sees 3.0.27 to be the best matching types version for the code package version you have installed. This is a consistency error on the part of the maintainers of the types package when it comes to publishing.Yea, I know why it happened, it is a dumb inconsistency error, the point is typesync shouldn’t probably match versions two major lvl higher than it is stated in the package.json. 1.8.1 -> 2.0 is wrong, 1.8.1 -> 3.0.27 is even more wrong. Wouldn’t it be a better idea to just skip these? It could save a lot of time for future visitors 😃
Anyway thanks a lot for this one, it could have saved me a lot of time! 😃