How to choose advance version?

[chairy11]

Help, please!

I want the react-fullstack-advanced version, so I use the following command
graphql create app_name --boilerplate react-fullstack-advanced

 But it always asked me to 'Choose GraphQL boilerplate project', and I had to choose the 'react-fullstack-basic',  because there is not option called  'react-fullstack-advance' ! 
 How can I choose the 'react-fullstack-advance' version？

[DevanB]

@chairy11

Thanks for submitting an issue! Looks like we haven't updated the choices. So sorry about that! We will get that updated today.

---

Update:

I opened graphql-cli PR 275. Will close this issue once the updated version of graphql-cli is released.

[chairy11]

Thank you ! I'm waiting for the amazing update !

[winterdelta]

Currently, running graphql create and selecting react-fullstack-advanced works. This issue seems to be resolved.

[localjo]

I'm running into this issue today. It looks like react-fullstack-advanced is missing from the latest version of graphql-cli. Adding it in manually, there seem to be some other problems with the boilerplate, so maybe something else is still missing.

[dancarlson]

I also am not able to find the react-fullstack-advanced and all other selectiond throw errorInstalling node dependencies for /home/dan/code/prisma/my-app/package.json... 00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'install'

[ericbahr]

Same error here.

[dancarlson]

Turns out it was a node version error... update node and graphql to fix

I also am not able to find the react-fullstack-advanced and all other selectiond throw errorInstalling node dependencies for /home/dan/code/prisma/my-app/package.json... 00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'install'

[drrckln]

@dancarlson Can you specify the versions that worked for you?

[chris-hailstorm]

I can't vouch for the current state of the react-fullstack-advanced boilerplate, but it's easy enough to enable that variant for the CLI tool. After an npm install of graphql-cli, just edit the boilerplate list in node_modules/graphql-cli/dist/cmds/create/boilerplates.js and add an entry in the same form as the ones for /minimal and /basic, then run graphql create.

Maybe the exclusion of the react-fullstack-advanced boilerplate was intentional because the boilerplate itself isn't ready; I can't tell. But the names and URLs are all hardwired in that file.

[MileanCo]

The advanced one still doesnt work for me, after installing as above by editing boilerplates.js

 yarn start
yarn run v1.22.0
$ react-scripts start

There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.

The react-scripts package provided by Create React App requires a dependency:

  "babel-eslint": "9.0.0"

Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-eslint was detected higher up in the tree:

  /Users/milean/workspace/reactnative/my-app-adv/node_modules/babel-eslint (version: 7.2.3) 

Manually installing incompatible versions is known to cause hard-to-debug issues.

If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.

To fix the dependency tree, try following the steps below in the exact order:

  1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
  2. Delete node_modules in your project folder.
  3. Remove "babel-eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
  4. Run npm install or yarn, depending on the package manager you use.

In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:

  5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
     This may help because npm has known issues with package hoisting which may get resolved in future versions.

  6. Check if /Users/milean/workspace/reactnative/my-app-adv/node_modules/babel-eslint is outside your project directory.
     For example, you might have accidentally installed something in your home folder.

  7. Try running npm ls babel-eslint in your project folder.
     This will tell you which other package (apart from the expected react-scripts) installed babel-eslint.

If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.

P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.