Ignite: Cannot create new app with Ignite 2

[phuongpt]

I don't know what's wrong here, no problem with version 1

[phuongpt]

I can create new project by ignite boilerplate-install ir-boilerplate abc, but got this error ([email protected])

[GantMan]

Hi @phuongpt - I was able to create an app with Ignite just now, with no problem.

From your first message I don't see any errors or any output at all!? Any feedback that can help?

As for the failed JEST tests, that's due to the enzyme not supporting 0.45.1 yet. AirBnB claims they will support it when React 16 is out of beta/alpha

[phuongpt]

FYI @GantMan

[jamonholmgren]

@phuongpt I probably wouldn't name your app app. Maybe try:

ignite new Foo --min

Does this work?

[nemoNoboru]

Got exactly the same issue.
ignite new Foo and ignite new Foo --min throws the same error:
undefined is not and object (evaluating 'regeneratorRuntime.mark')

[jamonholmgren]

@nemoNoboru Trying to spin one up now, back at you shortly.

[jamonholmgren]

Getting the same error. This has something to do with the generator function. Investigating.

[jamonholmgren]

This is related to https://github.com/ben-hunter-hansen/angular-async-await/issues/11.

They're also using regenerator: https://github.com/ben-hunter-hansen/angular-async-await/blob/master/dist/angular-async-await.js#L56

[jamonholmgren]

Well...I'm a bit stumped, and headed to bed. @skellock perhaps you have some ideas on this? Some dependency causing the generator engine to not be loaded?

[rochapablo]

+1

[JovanKanevche]

I have the same exact error
i updated my node to 8.10 like one hour ago
maybe that's the problem

[GantMan]

Yeah, I have node 7.7.4 on this laptop. I'll upgrade to 8.x and see if the issue comes from that.

[ernoaapa]

Had same problem as @phuongpt screenshot. Solved by changing how sagas are exported as described here https://github.com/facebook/react-native/issues/14838#issuecomment-313398604

In App/Sagas/index.js:

export default function * root () {

To:

const root = function * root () {
  // ... snip
export default root

And similar change to the both sagas.

Edit:
If someone more professional can explain should that export default function * root () { work and how to make it work, I would really appreciate.

[JeffreyJamesAttenti]

I am on Win 7 with nodejs 7.10.0 and I get the same issue when creating a new app with the --max flag.

[skellock]

It's because generators are not being compiled when they exist as functions, but they are if they're coerced into an expression and jammed into a variable first.

So as @ernoaapa points out above:

function * boo () {} is now 💩 but const yay = function * () {} is 👍 .

I believe this to be an upstream issue (upstream from react-native i mean), but haven't found the source just yet. I suspect it's a babel plugin that got upgraded recently that contains this bug. To target generators, your AST selectors would need to look for both function declarations and expressions.

My recommendation is to stay on 45.x short term.

But if that's not how you roll, convert your generators to be expressions.

Tricksy.

[skellock]

Ok, looks like facebook is on this issue, so I'm stepping off for now.

Another workaround is to delete your .babelrc file. Which sucks if you have valuable stuff in there.

I reckon this will be fixed shortly.

[jamonholmgren]

Yeah, just saw this tweet by @grabbou which seems to reference it: https://twitter.com/grabbou/status/882927535855722496

He recommends using Haul to fix it.

[skellock]

This issue was slightly different than the transform-runtime missing dependency though. Related though. This issue is an issue with Haul though. I tested that today.

[grabbou]

Thanks for CC-ing me here! I already answered in the react-native repository, this could've been fixed here: https://github.com/facebook/react-native/commit/e7c1cf5b7d2eba9468804635d0c2a0fc6725e42a

Haven't tested it - should be inside 0.47-rc.

[jamonholmgren]

Awesome, thanks @grabbou !

[hungdev]

@ernoaapa it still error

[benjaminhorner]

@jamonholmgren CC @grabbou : Any updates on this issue? The error is still there if you try with the demo project.

[grabbou]

Waiting for metro-bundler to release a new version with the fix and going
to bump it.

On Fri, 7 Jul 2017 at 16:30 Benjamin Horner [e-mail]
wrote:

@jamonholmgren https://github.com/jamonholmgren CC @grabbou
https://github.com/grabbou : Any updates on this issue? The error is
still there if you try with the demo project.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinitered/ignite/issues/1098#issuecomment-313698459,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWcxl5zPSC_4AMGKataLbsrefVEVHylks5sLkEOgaJpZM4OHvc6
.

[tastycode]

This definitely blocked me from being able to use Ignite for a project with a tight deadline. I tried the const foo = function * foo() trick and got a more cryptic error.

This is based on following the instructions in README.md (PizzaApp), then trying the fix above. Here's my full diff from what ignite-cli produced.

diff --git a/App/Sagas/GithubSagas.js b/App/Sagas/GithubSagas.js
index 2b562c3..b49547e 100644
--- a/App/Sagas/GithubSagas.js
+++ b/App/Sagas/GithubSagas.js
@@ -2,7 +2,8 @@ import { call, put } from 'redux-saga/effects'
 import { path } from 'ramda'
 import GithubActions from '../Redux/GithubRedux'

-export function * getUserAvatar (api, action) {
+
+const getUserAvatar = function * getUserAvatar (api, action) {
   const { username } = action
   // make the call to the api
   const response = yield call(api.getUser, username)
@@ -16,3 +17,5 @@ export function * getUserAvatar (api, action) {
     yield put(GithubActions.userFailure())
   }
 }
+
+export default getUserAvatar
diff --git a/App/Sagas/StartupSagas.js b/App/Sagas/StartupSagas.js
index 8cc37ae..0dd3207 100644
--- a/App/Sagas/StartupSagas.js
+++ b/App/Sagas/StartupSagas.js
@@ -6,7 +6,7 @@ import { is } from 'ramda'
 export const selectAvatar = (state) => state.github.avatar

 // process STARTUP actions
-export function * startup (action) {
+const startup = function * startup (action) {
   if (__DEV__ && console.tron) {
     // straight-up string logging
     console.tron.log('Hello, I\'m an example of how to log via Reactotron.')
@@ -38,3 +38,5 @@ export function * startup (action) {
     yield put(GithubActions.userRequest('GantMan'))
   }
 }
+
+export default startup
diff --git a/App/Sagas/index.js b/App/Sagas/index.js
index 18a9fd1..0793cc3 100644
--- a/App/Sagas/index.js
+++ b/App/Sagas/index.js
@@ -21,7 +21,7 @@ const api = DebugConfig.useFixtures ? FixtureAPI : API.create()

 /* ------------- Connect Types To Sagas ------------- */

-export default function * root () {
+const root = function * root() {
   yield [
     // some sagas only receive an action
     takeLatest(StartupTypes.STARTUP, startup),
@@ -30,3 +30,4 @@ export default function * root () {
     takeLatest(GithubTypes.USER_REQUEST, getUserAvatar, api)
   ]
 }
+export default root

I briefly tried bumping to 0.47rc-1 of react-native, but ran into another cryptic error. Most likely because i updated react-native inside package.json after ignite-cli already generated the project. I looked into forking ignite-cli to use the newer version from the beginning, but didn't see a direct dependency for react-native inside ignite's package.json. It wasn't immediately clear how to get ignite-cli to use a newer version of react-native for project generation.

If it helps, here's the output of ignite doctor

ignite doctor
System
  platform           darwin
  arch               x64
  cpu                4 cores                             Intel(R) Core(TM) i7-6660U CPU @ 2.40GHz
  directory          /Users/tastycode/dev/ConcrnClient

JavaScript
  node               8.1.3        /Users/tastycode/.nvm/versions/node/v8.1.3/bin/node
  npm                5.0.3        /Users/tastycode/.nvm/versions/node/v8.1.3/bin/npm
  yarn               0.27.5       /Users/tastycode/.nvm/versions/node/v8.1.3/bin/yarn

React Native
  react-native-cli   2.0.1
  app rn version     0.45.1

Ignite
  ignite             2.0.0        /Users/tastycode/.nvm/versions/node/v8.1.3/bin/ignite

Android
  java               1.8.0_131    /usr/bin/java
  android home       -            undefined

iOS
  xcode              8.3.3

Best of luck!

[fredbt]

Same issue happening here.

[fredbt]

For me, deleting .babelrc worked.

This was the content of the file generated by ignite CLI:

{
"presets": ["react-native"],
"env": {
"production": {
"plugins": ["ignite-ignore-reactotron"]
}
}
}

[jbreuer95]

I just downgraded babel-preset-react-native to 2.0.0 and got it working

[fredbt]

@jbreuer95 I had to do the same in another project.

[nikitph]

i cant get a created app to get to work . seems related. deleted babelrc and downgraded babel-preset-react-native to 2.0.0

[hungdev]

@nikitph just downgraded babel-preset-react-native to 2.0.0, don't need to delete babelrc file. Run npm install and react-native run-android. it worked for me.

[fyodorvi]

downgraded babel-preset-react-native to 2.0.0, still getting same error

[endru-ralali]

Yup, downgraded babel-preset-react-native to 2.0.0 works for me.

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

[hungdev]

you can clone and compair with your project. this project is clean.
https://github.com/hungdev/Revler

[devanshsadhotra]

@phuongpt
i faced the similar error using ignite,
i upgraded react-native version to "0.46.0" and down graded babel-preset-react-native to "2.0.0" and it worked fine

[kcalmes]

@fyodorvi Make sure to clear your caches.

watchman watch-del-all
rm -rf ./node_modules
rm -rf $TMPDIR/react-*
npm start -- --reset-cache

Make sure all of these commands complete successfully.

[fyodorvi]

@kcalmes thanks, cleaning the cache helped

[chrisbull]

Just installed ignite for the first time.
Was getting all the issues above.
What finally worked for me was essentially everything people mentioned above.

Step 1
In the package.json file, I changed
react-native to version 0.46.4 and
babel-preset-react-native to 2.0.0

Step 2
iOS Simulator -> Reset Content and Settings

Step 3

watchman watch-del-all
rm -rf $TMPDIR/react-*
rm -rf ios/build
rm -rf node_modules/ 
npm cache clean --force
yarn install
yarn start -- --reset-cache
react-native run-ios

[nikitph]

Aren't there smoke tests for this very thing. I mean I love ignite but this
might turn off new comers
On Wed, Jul 12, 2017 at 1:48 AM Chris [e-mail] wrote:

Just installed ignite for the first time.
Was getting all the issues above.
What finally worked for me was essentially everything people mentioned
above.

Step 1
In the package.json file, I changed
react-native to version 0.46.0 and
babel-preset-react-native to 2.0.0

Step 2
iOS Simulator -> Reset Content and Settings

Step 3

watchman watch-del-all
git clean -xdf
rm -rf $TMPDIR/react-*
yarn install
react-native run-ios

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinitered/ignite/issues/1098#issuecomment-314698028,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExqB3owlqbiJR3qiF-70D22Sptmwcjhks5sNIhegaJpZM4OHvc6
.

[jqn]

@nikitph you got that right. I wanted to start using ignite for a new project but I had to turn away because of this error.

[nikitph]

@jqn its really great.... i urge you to give another shot... although its ironic having to write this in an issue report

[zicrox]

I downgraded babel-preset-react-native to "2.0.0" and it worked fine without changing the react-native version.

[skellock]

Ya there was an upstream dependency upgrade that pretty much blew up the React Native universe. It was a bumpy few days.

I’ll take another look today at how we are referencing our dependencies.

[tmaly1980]

CAREFUL of @chrisbull 's commands, git clean -xdf will WIPE OUT any files not committed into the repo. I just lost a bunch of files. =(

[tmaly1980]

@skellock Wouldn't it be as simple as changing the package.json to specifically reference babel-preset-react-native to "2.0.0", rather than leaving people in limbo while we wait for those developers to fix that issue?

[skellock]

@tmaly1980 : yes, that sounds like a good plan. I'll give that a try.

[jqn]

Downgrading babel preset also worked for me
npm install --save [email protected]
npm install --save-dev [email protected]

[liambrownweb]

The babel preset solution seems to be hit and miss; some people are getting results, and some people aren't. I'm firmly in the latter camp with Node 8.1.4 on Linux; I've tried several times with brand-new test projects, and it hasn't worked yet.

[skellock]

I had no issues with Linux (elementary & node 8.1.4) here @liambrownweb. If you're upgrading, don't forget to run npm run start -- --reset-cache as there will be some babel cache artifacts ruining the party.

[juvasquezg]

Hi,

Not worked for my in Android.

react-native run-android

react-native 0.42
node 8.0.0
npm 5.3

When i run

react-native run-ios

It works perfect but not in Android.

[juvasquezg]

Hi,

Again

yarn add [email protected]

worked for me.

[liambrownweb]

@skellock Node 8.1.4 was the solution. Installed and ran with no problems. Definitely worth the trouble; you guys are doing a nice job with this tool.

I'm running OpenSuSE Leap 42.2 in a virtual machine. Same environment where I reported the failure to run earlier, but when I upgraded Node to 8.1.4, it started working. Anybody else, give me a thumbs-up if that version fixes the problem in your setup.

[jamonholmgren]

Awesome, thanks for the feedback @liambrownweb ! @phuongpt and others, is it okay to close this issue now?

[devanshsadhotra]

@jamonholmgren you may proceed

[bamne123]

Following commands worked for me.

ignite new
npm cache clean --force
react-native run-ios

[stempest0925]

My English is not very good, here is the machine translation.
This is a problem that may occur when the version downgrade 0.56 down 0.55.4, the version of babel-preset-react-native used is 2.1.0.

Resolution process:
Try to reduce the node version to 8, babel-preset-react-native is changed to 2.0.0, use native run-android and start --reset-cache will solve this problem.

Hope it works for you~