-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): [playground] correct issues with libs #5162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for the PR, @armano2! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
@bradzacher suggested change applied |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Checklist
Overview
Correct issue with loading libs between editor and code, "lib" resolution imitates to behavior
Changes
editor and linting is using now exact copy of typescript definitions.
there is no additional calls to cdn to retrieve type definitions, unless sandbox is not exposing types (old ts versions)
lib
, options can be provided in tsconfig and its going to be properly usedparsing and validation of tsconfig is done by typescript utils
ctrl+click on types defined in libs is now working correctly
lib: es6


lib: esnext
Test cases