Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

react-native-git-upgrade:ReferenceError: [BABEL] unknow option base.0. #17054

Closed
luckyly opened this issue Dec 4, 2017 · 1 comment
Closed
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@luckyly
Copy link

luckyly commented Dec 4, 2017

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Environment:
OS: Windows 10
Node: 6.11.3
Yarn: 1.0.2
npm: 3.10.10
Watchman: Not Found
Xcode: N/A
Android Studio: Not Found

Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: ^0.50.4 => 0.50.4

Target Platform: Android 6.0

Steps to Reproduce

When i use "react-native-git-upgrade",it happend.

Expected Behavior

react-native should be upgrade.

Actual Behavior

node_modules\babel-core\lib\transformation\file\logger.js:41
throw new Constructor(this._buildMessage(msg));
^

ReferenceError: [BABEL] C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\cliEntry.js: Unknown option: base.0. Ch
eck out http://babeljs.io/docs/usage/options/ for more information about options.

A common cause of this error is the presence of a configuration options object without the corresponding preset name. Example:

Invalid:
{ presets: [{option: value}] }
Valid:
{ presets: [['presetName', {option: value}]] }

For more detailed information on preset configuration, please see http://babeljs.io/docs/plugins/#pluginpresets-options.
at Logger.error (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation
\file\logger.js:41:11)
at OptionManager.mergeOptions (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib
transformation\file\options\option-manager.js:226:20)
at OptionManager.init (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transfor
mation\file\options\option-manager.js:368:12)
at File.initOptions (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transforma
tion\file\index.js:212:65)
at new File (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transformation\fil
e\index.js:135:24)
at Pipeline.transform (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\transfor
mation\pipeline.js:46:16)
at Object.transformFileSync (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-core\lib\ap
i\node.js:152:10)
at compile (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-register\lib\node.js:118:20)
at loader (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade\node_modules\babel-register\lib\node.js:144:14)
at Object.require.extensions.(anonymous function) [as .js] (C:\Users\www\AppData\Roaming\npm\node_modules\react-native-git-upgrade
\node_modules\babel-register\lib\node.js:154:7)

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

@stale
Copy link

stale bot commented Feb 2, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 2, 2018
@stale stale bot closed this as completed Feb 9, 2018
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

1 participant