Closed dylang closed 6 years ago
Currently typesync always adds the latest version of typings, but maybe it should look for a version that matches the semver of the package and write it out in the same format. That's more work though, and not sure if it's that valuable. If yarn upgrade-interactive still lists updates for packages with no prefixed version, I would not be opposed to making typesync write the exact version always.
That sounds like an even better idea, good thinking!
I always use prefixes so I don't know how yarn upgrade-interactive works in that case. Could you verify this for me please?
Implemented as of v0.4.0.
Amazing job, works great!
We use renovate to keep our dependencies up-to-date, and it recommends not including
^
or~
in the semver version inpackage.json
files so that it can test all version upgrades before merging them.yarn
has a setting for this:It would be helpful if
typesync
honored that config.There might be a similar setting for
npm
.