Update tsutils to the latest version 🚀#29
Conversation
Update to this version instead 🚀 Release Notes for v3.1.0Features:
CommitsThe new version differs by 8 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for v3.2.0Features:
|
Update to this version instead 🚀 Release Notes for v3.3.0Features:
Bugfixes:
CommitsThe new version differs by 6 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for v3.3.1Bugfixes:
|
Update to this version instead 🚀 Release Notes for v3.4.0Features:
|
Update to this version instead 🚀 Release Notes for v3.5.0Features:
|
Update to this version instead 🚀 Release Notes for v3.5.1Bugfixes:
|
Update to this version instead 🚀 Release Notes for v3.5.2Bugfixes:
|
Update to this version instead 🚀 Release Notes for v3.6.0Features:
|
Update to this version instead 🚀 Release Notes for v3.9.0Features:
CommitsThe new version differs by 12 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for v3.9.1Bugfixes:
|
Update to this version instead 🚀 Release Notes for v3.10.0Features:
Bugfixes:
|
Update to this version instead 🚀 Release Notes for v3.11.0Features:
CommitsThe new version differs by 12 commits.
See the full diff |
|
|
|
|
|
|
|
|
Version 3.0.0 of tsutils was just published.
The version 3.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of tsutils.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v3.0.0typescript@<2.8.0getIdentifierText,isJsxFramgment,ImportOptionsisModifierFlagSet,findImportsandgetControlFlowEnd'tsutils/util/util', import directly from'tsutils/util/control-flow'or'tsutils/util'isFunctionScopeBoundaryandisBlockScopeBoundarynow return a enum member ofScopeBoundaryinstead of a booleanisFunctionScopeBoundaryno longer returns a truthy value forInterfaceDeclaration,TypeAliasDeclarationFeatures:
isTypeScopeBoundaryreturningScopeBoundary.TypeorScopeBoundary.ConditionalTypeScopeBoundarySelectorwhose members can be used to determine if a declaration belongs to a givenScopeBoundaryby using bitwise ANDBugfixes:
collectVariableUsagenow correctly handlesinfer Tnested inside function signatures or mapped typesisCompilerOptionEnabledcorrectly handlesskipDefaultLibCHeckandsuppressImplicitAnyIndexErrorsCommits
The new version differs by 12 commits.
4099ae6v3.0.00f03549add node version requirement to package.json566e353isCompilerOptionEnabled: add contraint of suppressImplicitAnyIndexErrorsea59b1crequire typescript@2.8359bf07usage: InferType is correctly assiciated with ConditionalTypef4af733use Array.prototype.includes9636689remove deprecated stuffe49a4f7Merge branch 'master' into nexta84ccaaAdd ScopeBoundary.ConditionalType752c47cisCompilerOptionEnabled: add relationship of skip(Default)LibCheck5cc7276add isTypeScopeBoundarybd5c223breaking changesSee the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴