Skip to content
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

refactor: Remove skipLibCheck in TSConfig #564

Closed
danielbankhead opened this issue Jun 28, 2023 · 0 comments · Fixed by #574
Closed

refactor: Remove skipLibCheck in TSConfig #564

danielbankhead opened this issue Jun 28, 2023 · 0 comments · Fixed by #574
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: cleanup An internal cleanup or hygiene concern.

Comments

@danielbankhead
Copy link
Member

Context: #562 (comment)

@danielbankhead danielbankhead added semver: major Hint for users that this is an API breaking change. type: cleanup An internal cleanup or hygiene concern. priority: p3 Desirable enhancement or fix. May not be included in next release. next major: breaking change this is a change that we should wait to bundle into the next major version labels Jun 28, 2023
@danielbankhead danielbankhead changed the title Refactor!: Remove skipLibCheck in TSConfig refactor!: Remove skipLibCheck in TSConfig Jun 28, 2023
@danielbankhead danielbankhead changed the title refactor!: Remove skipLibCheck in TSConfig refactor: Remove skipLibCheck in TSConfig Jul 18, 2023
@danielbankhead danielbankhead removed semver: major Hint for users that this is an API breaking change. next major: breaking change this is a change that we should wait to bundle into the next major version labels Jul 18, 2023
@danielbankhead danielbankhead linked a pull request Jul 18, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant