An in-range update of typescript is breaking the build 🚨

[greenkeeper[bot]]

Version 2.4.1 of typescript just got published.

Branch	Build failing 🚨
Dependency	typescript
Current Version	2.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/maxdavidson/structly/builds/247610463?utm_source=github_status&utm_medium=notification)

---

Release Notes

TypeScript 2.4

For release notes, check out the release announcement

For new features, check out the What's new in TypeScript 2.4.

For breaking changes, check out the Breaking changes in TypeScript 2.4 page.

For the complete list of fixed issues, check out the fixed issues query for Typescript 2.4.

Download:

• npm
• Visual Studio 2015 plugin
• Visual Studio 2017 (Select new version in Tools/Options)
• NuGet package

Commits

The new version differs by 141 commits.

• 8b2fe13 Update LKG.
• 14d95ed Test:Block-scoped definition of Promise works
• a8846bf Skip block scope check with no error location
• 44f2336 Merge pull request #16633 from Microsoft/release-2.4_fixIncrementalParsing
• 4875a27 Add tests
• 15ef20d Set the structureReused to be safemoudles when dynamic import change
• 6d33083 Add tests
• 11b9f6e Wip-fix incremental parsing
• 2721fd4 In TypeScript code, never bind JSDoc normally, just set parent pointers (#16555) (#16561)
• 0968ed9 Revert string enum changes (#16569)
• 096f8cc Update LKG
• 9241175 Allow running in strict mode (#16557)
• f49b007 Update LKG
• f1b0f59 Update version to 2.4.1
• ed9cde9 Update LKG

There are 141 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 2.4.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

Version 2.4.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 3 commits.

• 6105867 Bumped version to 2.4.2.
• a34cf58 Update the builder dependency graph only if it was created.
• 50abee3 Never return undefined from getExportsOfModule (#17019)

See the full diff