fix(deps): update dependency react-app-polyfill to v0.2.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-app-polyfill	0.2.0 -> 0.2.2

---

Release Notes

facebook/create-react-app

v0.2.2

Compare Source

0.2.2 (August 22, 2016)

Build Dependency (react-scripts)

• When the bundle size changes, we now display the difference after build. (@​elijahmanor in #​340)
• npm installing a missing dependency now forces a rebuild. (@​gaearon in #​349)
• Autoprefixer config now includes more commonly supported browsers. (@​kripod in #​345)
• All the configuration is now documented inline so ejecting doesn’t leave you in the dark. (@​gaearon in #​362)
• Object.assign() polyfill is now bundled by default. (@​gaearon in #​399)
• React Native Web now works out of the box. (@​grigio in #​407)
• Same asset filenames in different folders don’t confuse the server now. (@​arunoda in #​446)
• The otf font format is now supported. (@​A-gambit in #​434)
• The new-cap linting rule has been disabled thanks to feedback from Immutable.js users. (@​rricard in #​470)

Migrating from 0.2.1 to 0.2.2

Update react-scripts to point to 0.2.2 in your package.json and run npm install. You shouldn’t need to do anything else.

Newly created projects will use 0.2.2 automatically. You don’t need to update the global create-react-app CLI itself. It stays at 0.2.0 for now because it doesn’t have any changes.

v0.2.1

Compare Source

0.2.1 (August 1, 2016)

Build Dependency (react-scripts)

• Fixes an issue with npm start taking a very long time on OS X with Firewall enabled (@​gaearon in #​319)
• Fixes an issue with Webpack eating a lot of CPU in some cases (@​dceddia in #​294)
• We now warn if you import a file with mismatched casing because this breaks the watcher (@​alexzherdev in #​266)
• CSS files specifying ?v= after asset filenames, such as Font Awesome, now works correctly (@​alexzherdev in #​298)
• Issues with npm linking react-scripts have been fixed (@​dallonf in #​277)
• We now use /static prefix for assets both in development and production (@​gaearon in #​278)

Migrating from 0.2.0 to 0.2.1

Update react-scripts to point to 0.2.1 in your package.json and run npm install. You shouldn’t need to do anything else. If you see a warning about wrong file casing next time you npm start, fix your imports to use the correct filename casing.

Newly created projects will use 0.2.1 automatically. You don’t need to update the global create-react-app CLI itself. It stays at 0.2.0 for now because it doesn’t have any changes.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.