mirror of
https://github.com/status-im/react-native.git
synced 2025-01-10 09:35:48 +00:00
bc74dd1e14
Summary: The iOS and Android native folders of a React Native app can be difficult to maintain. This introduces a new workflow for creating and maintaining the native code of your app. Now it will be possible to: 1. Remove the native iOS or Android folders 2. Create an `app.json` for your app, with at least a `name` and `displayName` 3. Run `react-native eject`, and the native code for your app will be generated Then, as usual, you can run `react-native run-ios` and `react-native run-android`, to build and launch your app For apps that don't have any native code, it will be possible to ignore the `ios` and `android` folders from version control. Eject step tested in RN app by deleting native folders. mkonicek, what is the best way to test `react-native init`? As follow-up items, we can enable the following: - Configuring app icon and launch screen from the `app.json` - Automatically run `react-native link` for native libraries - A Closes https://github.com/facebook/react-native/pull/12162 Differential Revision: D4509138 Pulled By: ericvicenti fbshipit-source-id: 0ee213e68f0a3d44bfce337e3ec43e5024bacc66
77 lines
1.9 KiB
JavaScript
77 lines
1.9 KiB
JavaScript
/**
|
|
* Copyright (c) 2015-present, Facebook, Inc.
|
|
* All rights reserved.
|
|
*
|
|
* This source code is licensed under the BSD-style license found in the
|
|
* LICENSE file in the root directory of this source tree. An additional grant
|
|
* of patent rights can be found in the PATENTS file in the same directory.
|
|
*
|
|
* @flow
|
|
*/
|
|
'use strict';
|
|
|
|
const { getProjectCommands } = require('./core');
|
|
|
|
import type { ConfigT } from './core';
|
|
|
|
export type CommandT = {
|
|
name: string,
|
|
description?: string,
|
|
usage?: string,
|
|
func: (argv: Array<string>, config: ConfigT, args: Object) => ?Promise<void>,
|
|
options?: Array<{
|
|
command: string,
|
|
description?: string,
|
|
parse?: (val: string) => any,
|
|
default?: (config: ConfigT) => any | any,
|
|
}>,
|
|
examples?: Array<{
|
|
desc: string,
|
|
cmd: string,
|
|
}>,
|
|
pkg?: {
|
|
version: string,
|
|
name: string,
|
|
},
|
|
};
|
|
|
|
const documentedCommands = [
|
|
require('./server/server'),
|
|
require('./runIOS/runIOS'),
|
|
require('./runAndroid/runAndroid'),
|
|
require('./library/library'),
|
|
require('./bundle/bundle'),
|
|
require('./bundle/unbundle'),
|
|
require('./eject/eject'),
|
|
require('./link/link'),
|
|
require('./link/unlink'),
|
|
require('./install/install'),
|
|
require('./install/uninstall'),
|
|
require('./upgrade/upgrade'),
|
|
require('./logAndroid/logAndroid'),
|
|
require('./logIOS/logIOS'),
|
|
require('./dependencies/dependencies'),
|
|
];
|
|
|
|
// The user should never get here because projects are inited by
|
|
// using `react-native-cli` from outside a project directory.
|
|
const undocumentedCommands = [
|
|
{
|
|
name: 'init',
|
|
func: () => {
|
|
console.log([
|
|
'Looks like React Native project already exists in the current',
|
|
'folder. Run this command from a different folder or remove node_modules/react-native',
|
|
].join('\n'));
|
|
},
|
|
},
|
|
];
|
|
|
|
const commands: Array<CommandT> = [
|
|
...documentedCommands,
|
|
...undocumentedCommands,
|
|
...getProjectCommands(),
|
|
];
|
|
|
|
module.exports = commands;
|