Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Use TypeScriptVersion.latest instead of "next" #279

Merged
merged 4 commits into from
Mar 23, 2020

Conversation

sandersn
Copy link
Member

Except when installing from npm. definitelytyped-header-parser has it right, but dtslint previously went through hoops to add "next" so that it could install typescript@next from npm. This PR reduces the scope of that addition to just installer.ts. Everywhere else just treats the next version as a normal version number.

dtslint installs the latest version of typescript as "next" because
that's the npm name.

Probably a better fix is to install typescript@next into a directory
with the same name as the rest, stripping off the .0-dev.20200323 part.
This removes the need to change the name when testing dependencies. I'm
not sure yet about when testing the main package.
Instead, just use TYpeScriptVersion.latest everywhere except when
installing from npm.
@sandersn sandersn merged commit 1bd4ce5 into master Mar 23, 2020
@sandersn sandersn deleted the convert-latest-to-next branch March 23, 2020 22:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant