Make TypeSync work without the typespublisher resource + use npm-registry-fetch
#97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Microsoft removed the typespublisher resource that TypeSync relies on as a type definition source, TypeSync stopped working.
TypeSync has been updated to no longer depend on that resource, and instead depends solely on the npm registry. This does mean that we lose the ability to semi-detect unused typings, since the "globals" list is not available to us anymore, so that feature has been removed.
Additionally, we are now using
npm-registry-fetchwhich should give us authentication, retries, and registry selection for free.Closes #96, #89, and #67