Update react-scripts-ts: 2.8.0 → 2.17.0 (minor)

[depfu]

⚠️ No CI detected ⚠️

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Our friends at Travis-CI provide excellent service.
• Circle CI are good, too, and have a free plan that will cover basic needs.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to be properly detected.

---

We've updated a dependency and here is what you need to know:

name	version specification	old version	new version
react-scripts-ts	^2.6.0	2.8.0	2.17.0

Additionally, the update changed a few other dependencies as well:

action	name	old version	new version
updated	typescript	2.5.3	2.6.2
updated	typescript	2.5.3	2.6.2

You should probably take a good look at the info here and the test results before merging this pull request, of course.

What changed?

✳️ react-scripts-ts (2.8.0 → 2.17.0) · Repo · Changelog

✳️ typescript (2.5.3 → 2.6.2) · Repo

Release Notes

From the Github release:

This release includes:

• Support for JSX Fragments.
• Bug fixes reported against TypeScript 2.6.1.

Download:

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

[brianlovin]

@mxstbr added depfu here, but guess I should have checked with you first: do we want this repo to be maintained and updated?