This repository was archived by the owner on Nov 16, 2023. It is now read-only.
Document banned npm names #351
Closed
Conversation
This file contains hidden or 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
See also microsoft#349 and microsoft#350. As soon as an official decision for this issue exists, that should be referenced in the docs as well.
sandersn
suggested changes
Jan 10, 2022
Member
sandersn
left a comment
sandersn
left a comment
There was a problem hiding this comment.
Can you please make this change in microsoft/DefinitelyTyped-tools instead? I moved this package into that monorepo last month but ran out of time to freeze this repo before holidays.
LinqLover
added a commit
to LinqLover/DefinitelyTyped-tools
that referenced
this pull request
Jan 15, 2022
Cherry-picked from microsoft/dtslint@1ed6a62 Resolves microsoft/dtslint#351 (comment) by @sandersn
Author
|
Please see microsoft/DefinitelyTyped-tools#381. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
See also #349 and #350. As soon as an official decision for this issue exists, that should be referenced in the docs as well.