Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
0.8.0 (December 3, 2016)
🚀 New Feature
Linter warnings and errors are now checked during a continuous integration build (set by the
CIenvironment variable) and the build will fail if any issues are found. See Continuous Integration for more information.
Yarn is a new fast, reliable and secure alternative to the
npmclient. If you have Yarn installed,
create-react-appwill use it to install packages when you create an app. It also creates a
yarn.lockfile that should be checked into source control (e.g. git). This ensures the same versions of packages will be installed each time
yarn installis run, on any machine.
react-scriptsnow also displays instructions using
yarncommands for projects using Yarn (projects having a
To create a project using Yarn, simply install
npm install -g yarn create-react-app@latest create-react-app my-app # Packages are now installed with Yarn.
💥 Breaking Change
Object rest spread and JSX now use the native
Object.assign()method instead of Babel's helper function. If you are using
babel-preset-react-appdirectly in your project and targeting browsers that don't have
Object.assign()available, from now on you need a polyfill for it (e.g.
react-scriptsalready adds this polyfill, so no changes are necessary in Create React App projects.
🐛 Bug Fix
Fixes a bug in ejected configuration.
.babelrcfile in a parent directory interfering with the
Fixes a bug where
ejectfailed when a
configfolder already existed in the project.
react-scriptsnow treats imports with any unknown file extension as a resource. Files with a size below 10 KB are inlined using a data URI and larger files copied to the build folder. This removes the need for an internal whitelist of supported file extensions. Any file that's not JS or CSS is now handled the same way.
The test script now considers all files in the project when calculating test coverage.
react-scriptscan guess which process is running on the port 3000 when it's not available:
Something is already running on port 3000. Probably: my-app in /Users/ian/dev/my-app Would you like to run the app on another port instead?
- #1126 Add a note about vscode-jest. (@orta)
- #1080 Add a note for OSX users about watchman and jest. (@dmr)
- #1071 Adds to docs - deployment with S3/CloudFront. (@marcgarreau)
- #976 Added info on using global variables. (@jhorneman)
- #996 Remove redundant
functionfrom export statement. (@gnowoel)
- #959 Always build before deploying to gh-pages. (@dsernst)
- #974 Gently nudge users towards https by default. (@Swizec)
- Adam Stankiewicz (sheerun)
- Alice Rose (heldinz)
- Arunoda Susiripala (arunoda)
- Brian Ng (existentialism)
- Daniel Rech (dmr)
- Dave Ceddia (dceddia)
- David Ernst (dsernst)
- Dirk-Jan Rutten (excitement-engineer)
- Einar Löve (einarlove)
- Fabrizio Castellarin (EnoahNetzach)
- Fatih (frontsideair)
- Ian McNally (ianmcnally)
- Jurie Horneman (jhorneman)
- Kyle Mathews (KyleAMathews)
- Leo Wong (gnowoel)
- Marc Garreau (marcgarreau)
- Nazim Hajidin (nhajidin)
- Orta (orta)
- Patrick Mackinder (pmackcode)
- Sandro Padin (spadin)
- Sathish (bboysathish)
- Stefan (bebbi)
- Swizec Teller (Swizec)
- Vadzim (vadzim)
- Vesa Laakso (valscion)
- Ville Immonen (fson)
Migrating from 0.7.0 to 0.8.0
You may optionally update the global command (it’s not required, but it adds Yarn support for new projects):
npm install -g email@example.com
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact firstname.lastname@example.org