Update tsutils to the latest version 馃殌 - #88
Open
greenkeeper[bot] wants to merge 1 commit into
Open
Conversation
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.
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鈥檛 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鈥檛 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鈥檛 help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 馃尨