Open
Conversation
cab7755 to
fa9f440
Compare
Added explicit `import * as ts` statements across plugin source files instead of declaring it globally. See #227 (comment)
fa9f440 to
07e6e95
Compare
Owner
|
merge if its ready to merge |
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
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.
Changes
ts-expose-internalsto 5.6.3tsimports across ~80 files — Every plugin source file now has an explicitimport * as ts from 'typescript/lib/tsserverlibrary'instead of relying on the old ambient global. The oldts.d.tsis deletedglobals.d.tsrewritten to use a properdeclare global {}block, making the ambient/global boundary explicit and compatible with TS 5.9@typescript-eslint/no-restricted-importsrule that bannedtypescript*imports removed, since direct imports are now the intended patternNotes