Skip to content

Latest commit

 

History

History
164 lines (101 loc) · 8.8 KB

CHANGELOG.md

File metadata and controls

164 lines (101 loc) · 8.8 KB
Raw

Changelog

Unpublished

🐛 Bug fixes

  • Skip creating a git repo when inside existing repo (#920 by @byCedric)

3.0.0 - 2020-04-16

Create React Native App is revived as a bare-bones npx package that can be used to start an opinionated bare-workflow universal React Native project.

2.0.1 - 2018-09-21

This release merges Create React Native App with Expo CLI.

  • Expo CLI is a tool based on CRNA, made by the same team
  • It has all the same features, plus some additional benefits
  • Like CRNA, Expo CLI does not require an Expo user account
  • The create-react-native-app command will continue to work

The separate react-native-scripts package is now deprecated: new projects created with create-react-native-app will use Expo CLI instead of react-native-scripts. In addition to everything provided by CRNA, Expo CLI includes these extras:

  • Web-based user interface: in addition to the CLI, there's a GUI where you can view logs, launch the app on your devices or simulators, and publish updates.
  • Standalone app builds: you can build IPA and APK packages for deploying to App Store and Play Store without using Xcode or Android Studio.
  • Publishing: you can push updates to your deployed apps and optionally publish your app to Expo.io.
  • Tunnel: your physical device doesn’t need to be in the same wi-fi as your computer to be able to develop using it.
  • Optional user accounts: logging in allows listing all your projects in development in the Expo app without having to scan any QR codes and enables additional features like standalone builds. However, just like CRNA, Expo CLI can also be used without a user account.

Why are we bringing these two tools together?

  • Just one tool to learn: previously developers would start with CRNA and then switch to exp or XDE for additional features like standalone builds. Expo CLI is as easy to get started with as CRNA, but also supports everything previously offered by these separate tools.
  • Less confusing options: CRNA apps have always been loaded using the Expo app and able to use the Expo APIs in addition to the core React Native APIs. Users are sometimes confused about the differences between plain React Native, CRNA and Expo apps created with tools like exp or XDE. Installing the expo-cli package will make it clearer the additional functionality is provided by Expo.
  • Developer experience: Expo CLI is ahead of CRNA in terms of features and developer experience, and we’re continuously improving it.
  • Maintenance: having these two projects as separate codebases requires more maintenance and CRNA has previously falled behind because of this. A single codebase helps us keep it up to date and fix issues as fast as possible.

Upgrading from 1.14.0 to 2.0.1

All apps created with create-react-native-app, are compatible with Expo CLI without changes.

Upgrade react-native-scripts to v2.0.1 with:

npm install --save --save-exact [email protected]

or

yarn add --exact [email protected]

When you run npm start for the first time, Expo CLI will be installed.

Because react-native-scripts is now a wrapper for Expo CLI, you can also follow these steps to remove it from your project and use Expo CLI directly:

  1. Replace react-native-scripts with expo in the scripts config in package.json. Example: 
    "scripts": {
  "start": "expo start",
  "eject": "expo eject",
  "android": "expo start --android",
  "ios": "expo start --ios",
  "test": "jest"
}
  2. Remove react-native-scripts from devDependencies.

1.14.0 - 2018-04-27

Update Expo SDK 27.

1.12.1 - 2018-03-20

Update XDL to version 48.1.2.

1.12.0 2018-03-29

🎉 New features

1.11.1 - 2018-01-26

🎉 New features

Update XDL to version 48.0.2. (c671c7a by @fson)

1.10.0 - 2018-01-18

🎉 New features

1.9.0 - 2018-01-17

🎉 New features

1.8.0 - 2017-11-27

🎉 New features

1.7.0 - 2017-11-02

Release notes for previous releases between 1.3.1 and 1.7.0 were not include here as they only included React Native version bumps.

🐛 Bug fixes

1.3.1 - 2017-09-02

🐛 Bug fixes

  • Fix an issue where stdout is null when validating inotify watches in some rare cases that I don't understand yet. (ed4f5f4 by @brentvatne)

1.3.0 - 2017-08-28

🐛 Bug fixes

  • Force installation of Expo fork of react-native when ejecting to ExpoKit. (cbf3f9e by @brentvatne)

1.2.1 - 2017-08-19

🐛 Bug fixes

1.1.0 - 2017-07-28

🐛 Bug fixes

  • Switch Babel preset on eject (#328 by @fson)
  • Fix yarnpkg alias usage in the init script (#329 by @fson)

🎉 New features

  • Add interactive mode with keyboard commands (#326 by @fson)
  • Include whether dev or production is enabled in "Running app on" message (6559600 by @brentvatne)

1.0.0 - 2017-07-24

🐛 Bug fixes

🎉 New features

  • Add --package-manager option which allows you to specify any package manager to use when creating a project. (#307 by @metheglin)
  • Update to Expo SDK 19 / React Native 0.46.1. (63d1ddb by @brentvatne)
  • Softens warnings for npm 5 where version > 5.0.3. (#317 by @DuncanMacWeb)
  • Add CHANGELOG.md (#319 by @shashkovdanil)
  • Update xdl
    • Removes the dependency on ngrok and dtrace, so there is no native compile step on install.