question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npx ignite-cli new MyApp failed

See original GitHub issue

What’s going on? ignite-cli cannot init/new project

Steps to reproduce

  1. just run npx ignite-cli new MyApp `

dengjianyuan@Jerrys-MacBook-Pro ~ npx ignite-cli new MyApp
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·

█ Creating MyApp using Ignite 7.10.6
█ Powered by Infinite Red - https://infinite.red
█ Using ignite-cli with yarn
█ Bundle identifier: com.MyApp
────────────────────────────────────────────────

🔥 Igniting app
🖨  3D-printing a new React Native app
⠴ Unboxing npm dependencies

/Users/dengjianyuan/.npm/_npx/58859/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13 throw up; ^ warning expo > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. warning expo > expo-constants > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. warning expo > expo-file-system > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. warning expo > fbemitter > fbjs > core-js@1.2.7: core-js@❤️.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. warning react-native > @react-native-community/cli-platform-ios > xcode > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated warning react-native > @react-native-community/cli > @react-native-community/cli-plugin-metro > metro-core > jest-haste-map > sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added warning react-native > @react-native-community/cli > @react-native-community/cli-plugin-metro > metro > metro-minify-uglify > uglify-es@3.3.9: support for ECMAScript is superseded by uglify-js as of v3.13.0 warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated warning @storybook/react-native-server > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. warning @storybook/react-native-server > webpack > watchpack > watchpack-chokidar2 > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies warning @storybook/react-native-server > webpack > watchpack > watchpack-chokidar2 > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2. warning @storybook/react-native-server > @storybook/core > react-dev-utils > fork-ts-checker-webpack-plugin > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies warning @storybook/react-native-server > @storybook/core > webpack-dev-middleware > webpack-log > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. warning @storybook/react-native-server > @storybook/core > webpack-hot-middleware > querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. warning @storybook/react-native-server > webpack > node-libs-browser > url > querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. warning @storybook/react-native-server > @storybook/ui > @storybook/components > popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-syntax-highlighter > highlight.js@9.18.5: Support has ended for 9.x series. Upgrade to @latest warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper > popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-syntax-highlighter > lowlight > highlight.js@9.13.1: Version no longer supported. Upgrade to @latest warning detox > tempfile > uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. warning solidarity > gluegun > apisauce > axios@0.16.2: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410 warning solidarity > gluegun > enquirer > set-value@1.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version. warning solidarity > gluegun > prompt-autocompletion > prompt-choices > set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. warning solidarity > gluegun > enquirer > prompt-question > prompt-choices > set-value@1.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version. warning “react-native > react-native-codegen > jscodeshift@0.11.0” has unmet peer dependency “@babel/preset-env@^7.1.6”. warning “reactotron-react-native > react-native-flipper@0.34.0” has incorrect peer dependency “react@^16.8.1”. warning “reactotron-react-native > react-native-flipper@0.34.0” has incorrect peer dependency “react-native@^0.62.0”. warning " > @rnx-kit/metro-config@1.2.28" has unmet peer dependency “metro-config@>=0.58.0”. warning “@rnx-kit/metro-config > @rnx-kit/babel-preset-metro-react-native@1.0.17” has unmet peer dependency “metro-react-native-babel-preset@". warning “@storybook/react-native-server > @storybook/api@5.3.21” has unmet peer dependency "regenerator-runtime@”. warning “@storybook/react-native > @storybook/addons > @storybook/api > @reach/router@1.3.4” has incorrect peer dependency “react-dom@15.x || 16.x || 16.4.0-alpha.0911da3”. warning " > babel-loader@8.2.2" has unmet peer dependency “webpack@>=2”. warning " > detox@19.3.0" has unmet peer dependency “jest-environment-node@>=25.0.0”. warning " > detox@19.3.0" has unmet peer dependency “mocha@>=6.0.0”. error Command failed with exit code 1.

(Use node --trace-uncaught ... to show where the exception was thrown) `


npx ignite-cli doctor results: ~ npx ignite-cli doctor
`System platform darwin
arch x64
cpu 12 cores Intel® Core™ i7-9750H CPU @ 2.60GHz directory dengjianyuan /Users/dengjianyuan

JavaScript (and globally-installed packages) node 14.17.0 /Users/dengjianyuan/.nvm/versions/node/v14.17.0/bin/node npm 6.14.13 /Users/dengjianyuan/.nvm/versions/node/v14.17.0/bin/npm
@tarojs/cli 3.3.9
@vue/cli 4.5.14
eBriefcase 0.0.5
expo-cli 4.13.0
npm 6.14.13
yarn 1.22.10
yarn 1.22.10 /Users/dengjianyuan/.nvm/versions/node/v14.17.0/bin/yarn create-strapi-app 3.6.3
ignite-cli 3.5.2
storybook 5.3.19
wml 0.0.83
pnpm - not installed

Ignite ignite-cli 7.10.6 /Users/dengjianyuan/.npm/_npx/75845/bin/ignite
ignite src build /Users/dengjianyuan/.npm/_npx/75845/lib/node_modules/ignite-cli/build

Android java 1.8.0_252 /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/bin/java android home - /Users/dengjianyuan/Library/Android/sdk

iOS xcode 13.1
cocoapods 1.10.1 /usr/local/bin/pod `

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:27 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
kentond18commented, Aug 23, 2022

@frankcalise Yes, I have now, and all is working. Thank you!

1reaction
donfourcommented, Jun 3, 2022

bump, same issue on mac

Read more comments on GitHub >

github_iconTop Results From Across the Web

ignite-cli - npm
Troubleshooting · Make sure you are using the LTS version of Node. · If the installation fails because of an Xcode error (missing...
Read more >
Using TypeScript - React Native
If you're starting a new project, there are a few different ways to get started. ... If the above command is failing, you...
Read more >
TypeError: cb.apply is not a function - Stack Overflow
An Ubuntu 20.04 user here with node 16.0.0. I was getting the same error when I would run: > npx create-react-app [my app]....
Read more >
Creating your first build - Expo Documentation
Learn how to create a build for your app with EAS Build. ... You may alternatively use npx eas-cli , just remember to...
Read more >
How to Use React Native Ignite Boilerplate - Morioh
To start off, you can create a new Ignite project using the following command: npx ignite-cli new HealthTracker. This will generate a new...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found