Creating new project fails #12542

jeroenbourgois · 2017-02-23T13:36:31Z

Description

I did a fresh install following the instructions on https://facebook.github.io/react-native/docs/getting-started.html#content, but it fails at the first step:

react-native init AwesomeProject

This results in this output (the packages are installed properly with yarn):

├─ yargs-parser@4.2.1
└─ yargs@6.6.0
✨  Done in 5.86s.
/private/tmp/test/AwesomeProject/node_modules/babel-core/lib/transformation/file/index.js:600
      throw err;
      ^

SyntaxError: /private/tmp/test/AwesomeProject/node_modules/react-native/packager/react-packager/src/node-haste/index.js: You can only use Class Properties when the 'classProperties' plugin is enabled. (389:2)
  387 |   }
  388 |
> 389 |   static Cache;
      |   ^
  390 |   static Module;
  391 |   static Polyfill;
  392 |   static getAssetDataFromName;
    at Parser.pp$5.raise (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:4380:13)
    at Parser.pp$1.parseClassProperty (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:2508:10)
    at Parser.parseClassProperty (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:5947:20)
    at Parser.pp$1.parseClassBody (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:2424:34)
    at Parser.pp$1.parseClass (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:2361:8)
    at Parser.pp$1.parseStatement (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:1798:19)
    at Parser.parseStatement (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:5719:22)
    at Parser.pp$1.parseBlockBody (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:2223:21)
    at Parser.pp$1.parseTopLevel (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:1733:8)
    at Parser.parse (/private/tmp/test/AwesomeProject/node_modules/babylon/lib/index.js:1628:17)

Additional Information

I first thought it was a node problem so I reverted from 7.6.0 to the 6.10.0 LTS version, same result.

React Native version: ->

react-native-cli: 2.0.1
react-native: n/a - not inside a React Native project directory

Platform: both
Operating System: MacOS

The text was updated successfully, but these errors were encountered:

kafkadev · 2017-02-23T13:45:42Z

+1

odemolliens · 2017-02-23T13:47:08Z

+1

Kraignos · 2017-02-23T13:47:47Z

+1

jmz331 · 2017-02-23T13:51:21Z

+1 same problem.

UtkarshPramodGupta · 2017-02-23T13:51:34Z

+1

kumarpatel · 2017-02-23T13:52:26Z

+1

aliuspetraska · 2017-02-23T13:54:04Z

+1

BuiTruongXuan · 2017-02-23T13:54:20Z

+1

simonjk · 2017-02-23T13:56:06Z

+1

zphhhhh · 2017-02-23T13:56:29Z

+1

marcosiino · 2017-02-23T13:57:28Z

Lol, i'm just trying ReactNative now, and saw this strange error...so i've found this. Perfect timing! :) Btw, since i'm a beginner in ReactNative (just trying it now), how can i install the previous version of the cli which is not affect by this bug, using brew on mac, so that in the meanwhile i can try it ? (i've already installed the last cli, so i don't know if i first need to remove it). Someone can help me? Thanks!

nikolay-radkov · 2017-02-23T13:58:55Z

+1

idancali · 2017-02-23T14:00:46Z

+5 (the entire team is frustrated)

bluedusk · 2017-02-23T14:02:30Z

+1

agenciafera · 2017-02-23T14:03:02Z

+1

KaanErkol · 2017-02-23T14:09:01Z

+1

aliuspetraska · 2017-02-23T14:09:36Z

@grabbou please take a look

TheBlackHacker · 2017-02-23T14:13:30Z

+1

simonjk · 2017-02-23T14:14:41Z

This change was done on the file in question 3h ago so it should be the primary suspect:
4a4dddb

gmh04 · 2017-02-23T14:16:19Z

+1

gamer496 · 2017-02-23T14:16:55Z

+1

vaxo-m · 2017-02-23T14:17:54Z

+1

idancali · 2017-02-23T14:18:43Z

Found the bug people. Babylon (6.16.0 published an hour ago) messed something up. If you use 6.15.0 it works.

So if you just add this to your dependencies in your package.json file, you're good to go.

"babylon": "6.15.0"

grabbou · 2017-02-23T14:19:15Z

Thanks, will let the team know we got a problem.

Follow: https://twitter.com/grabbou/status/834770049382629377

kumarpatel · 2017-02-23T14:22:23Z

npm uninstall babylon && npm install babylon@6.15.0

craigedmunds · 2017-02-23T14:22:41Z

+1

carlosroberto555 · 2017-02-23T14:28:36Z

+1

MoOx · 2017-02-23T14:29:31Z

Stop +1 noise. Thanks.

shmakovdima · 2017-02-23T14:31:20Z

+1

sunruh · 2017-02-23T14:34:26Z

@hzoo I suspect it to come from PR babel/babylon#300

The changelog states

Don't parse class properties without initializers when classProperties is disabled and Flow is enabled (#300) (Andrew Levine)

Ensure that you enable the classProperties plugin in order to enable correct parsing of class properties. Prior to this version it was possible to parse them by enabling the flow plugin but this was not intended the behaviour.

If you enable the flow plugin you can only define the type of the class properties, but not initialize them.

hzoo · 2017-02-23T14:35:42Z

Awesome, need to figure out what react-native is doing

gelashviligiorgi · 2017-02-23T14:35:43Z

+1

markudevelop · 2017-02-23T14:36:15Z

@kumarpatel doesn't seems to work for me any other ideas for temp fix?

diegorodriguesvieira · 2017-02-23T14:36:55Z

+1

codelinter · 2017-02-23T14:39:28Z

Operating System: Windows 10 64bit

chapati23 · 2017-02-23T14:41:24Z

temp fix possibly forking react-native and restraining babylon version to 6.15 in the 2 package.json's?
•

react-native/package.json

Line 142 in 564126f

"babylon": "^6.14.1",

•

react-native/packager/package.json

Line 18 in 13edf6d

"babylon": "^6.14.1",

simonjk · 2017-02-23T14:42:21Z

was there any change. it is working now for me including babylon 6.16
$ npm list | grep react-native
├─┬ babel-preset-react-native@1.9.1
├─┬ react-native@0.41.2
$ npm list | grep babylon
│ ├── babylon@6.16.0

chapati23 · 2017-02-23T14:44:05Z

interesting, what os / node / react-native-cli versions @simonjk ?

hzoo · 2017-02-23T14:47:45Z

Yes the workaround should be to pin to babylon@6.15.0

Ok I have to work, so going to revert the 2 PRs and do a patch.

EDIT: Interesting how many people rely on Babel without any full time people working on it

dfischer · 2017-02-23T14:48:38Z

(sorry for OT) Well, if there's one thing to say it's interesting (and awesome) to see how many people are trying to get up and running with a tutorial and at the frequency. I just ran into this too. 👍 thanks for the quick response @hzoo

rizwanahmed19 · 2017-02-23T14:49:39Z

+1

hzoo · 2017-02-23T14:52:21Z

Yeah @dfischer, I'm really sorry this is the experience people get when starting out with react-native/javascript/open source. We make mistakes

dfischer · 2017-02-23T14:53:49Z

It's all good, I think it's cool how many people are reporting in. Good work @hzoo you rock!

robdonn · 2017-02-23T14:55:14Z

@hzoo Actually I think this is a really good experience for new people because it shows how quickly a problem can get resolved in a well supported project.

hzoo · 2017-02-23T14:56:22Z

Releasing v6.16.1 until we actually can get the time to figure this out.

Ok made a new patch release that just reverts the PRs that caused the issues.

If you need to you'll need to rm -rf node_modules and npm install again. You don't need to add babylon to dependencies if you did before if this fixes it.

report back if it's fixed*

futurechallenger · 2017-02-23T14:57:17Z

cool! @hzoo

zyhou · 2017-02-23T14:58:48Z

Good for me, it's work :)

Thanks @hzoo

RemoteCTO · 2017-02-23T15:00:03Z

🎉 - Back in business!

Using yarn v0.20.3
Installing react-native...
...
...
✨  Done in 9.76s.
To run your app on iOS:
...

kafkadev · 2017-02-23T15:02:29Z

Thanks @hzoo

sunruh · 2017-02-23T15:04:59Z

@simonjk @chapati23 If the haste map has been generated once with a babylon version that's working and no change requires regeneration, it keeps workng even if you upgrade babylon again.

simonjk · 2017-02-23T15:09:12Z

@chapati23 MacOS 10.11.6

react-native --version
react-native-cli: 2.0.1
react-native: 0.41.2

node --version
v7.4.0

had the problem first too but after a rm of the folder and a re-init it the problem was suddenly gone

jeroenbourgois · 2017-02-23T16:12:38Z

@hzoo @grabbou and everyone involved: thanks! Amazing how fast this was resolved!

idancali mentioned this issue Feb 23, 2017

6.16.0 releases is buggy - Please take a look babel/babylon#373

Closed

mcmillan mentioned this issue Feb 23, 2017

You can only use Class Properties when the 'classProperties' plugin is enabled #12545

Closed

dupuchba mentioned this issue Feb 23, 2017

Problem getting started drapanjanas/re-natal#90

Open

satya164 closed this as completed Feb 23, 2017

hzoo mentioned this issue Feb 23, 2017

Remove +1, -1 babel/babel-bot#18

Closed

danez mentioned this issue Feb 23, 2017

Include syntax-class-properties in packager #12550

Closed

facebook locked as resolved and limited conversation to collaborators May 24, 2018

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 19, 2018

Creating new project fails #12542

Creating new project fails #12542

Comments

jeroenbourgois commented Feb 23, 2017

Description

Additional Information

kafkadev commented Feb 23, 2017

odemolliens commented Feb 23, 2017

Kraignos commented Feb 23, 2017

jmz331 commented Feb 23, 2017

UtkarshPramodGupta commented Feb 23, 2017

kumarpatel commented Feb 23, 2017

aliuspetraska commented Feb 23, 2017

BuiTruongXuan commented Feb 23, 2017

simonjk commented Feb 23, 2017

zphhhhh commented Feb 23, 2017

marcosiino commented Feb 23, 2017

nikolay-radkov commented Feb 23, 2017

idancali commented Feb 23, 2017

bluedusk commented Feb 23, 2017

agenciafera commented Feb 23, 2017

KaanErkol commented Feb 23, 2017

aliuspetraska commented Feb 23, 2017

TheBlackHacker commented Feb 23, 2017

simonjk commented Feb 23, 2017 • edited Loading

gmh04 commented Feb 23, 2017

gamer496 commented Feb 23, 2017

vaxo-m commented Feb 23, 2017

idancali commented Feb 23, 2017 • edited Loading

grabbou commented Feb 23, 2017 • edited Loading

kumarpatel commented Feb 23, 2017

craigedmunds commented Feb 23, 2017

carlosroberto555 commented Feb 23, 2017

MoOx commented Feb 23, 2017

shmakovdima commented Feb 23, 2017

sunruh commented Feb 23, 2017

hzoo commented Feb 23, 2017

gelashviligiorgi commented Feb 23, 2017

markudevelop commented Feb 23, 2017 • edited Loading

diegorodriguesvieira commented Feb 23, 2017

codelinter commented Feb 23, 2017

chapati23 commented Feb 23, 2017

simonjk commented Feb 23, 2017 • edited Loading

chapati23 commented Feb 23, 2017

hzoo commented Feb 23, 2017 • edited Loading

Yes the workaround should be to pin to babylon@6.15.0

Ok I have to work, so going to revert the 2 PRs and do a patch.

dfischer commented Feb 23, 2017 • edited Loading

rizwanahmed19 commented Feb 23, 2017

hzoo commented Feb 23, 2017 • edited Loading

dfischer commented Feb 23, 2017

robdonn commented Feb 23, 2017

hzoo commented Feb 23, 2017 • edited Loading

Releasing v6.16.1 until we actually can get the time to figure this out.

futurechallenger commented Feb 23, 2017

zyhou commented Feb 23, 2017

RemoteCTO commented Feb 23, 2017

kafkadev commented Feb 23, 2017

sunruh commented Feb 23, 2017

simonjk commented Feb 23, 2017

jeroenbourgois commented Feb 23, 2017

simonjk commented Feb 23, 2017 •

edited

Loading

idancali commented Feb 23, 2017 •

edited

Loading

grabbou commented Feb 23, 2017 •

edited

Loading

markudevelop commented Feb 23, 2017 •

edited

Loading

simonjk commented Feb 23, 2017 •

edited

Loading

hzoo commented Feb 23, 2017 •

edited

Loading

dfischer commented Feb 23, 2017 •

edited

Loading

hzoo commented Feb 23, 2017 •

edited

Loading

hzoo commented Feb 23, 2017 •

edited

Loading