ignite
ignite copied to clipboard
infinitered
npx ignite-cli new MyApp failed
What's going on? ignite-cli cannot init/new project
Steps to reproduce
- 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: core-js@<3.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 > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: https://github.com/lydell/resolve-url#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: See https://github.com/lydell/source-map-url#deprecated
warning @storybook/react-native-server > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > webpack > node-libs-browser > url > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > @storybook/ui > @storybook/components > [email protected]: 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 > [email protected]: Support has ended for 9.x series. Upgrade to @latest
warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper > [email protected]: 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 > [email protected]: Version no longer supported. Upgrade to @latest
warning detox > tempfile > [email protected]: 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 > [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
warning solidarity > gluegun > enquirer > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning solidarity > gluegun > prompt-autocompletion > prompt-choices > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning solidarity > gluegun > enquirer > prompt-question > prompt-choices > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning "react-native > react-native-codegen > [email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react@^16.8.1".
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react-native@^0.62.0".
warning " > @rnx-kit/[email protected]" has unmet peer dependency "metro-config@>=0.58.0".
warning "@rnx-kit/metro-config > @rnx-kit/[email protected]" has unmet peer dependency "metro-react-native-babel-preset@".
warning "@storybook/react-native-server > @storybook/[email protected]" has unmet peer dependency "regenerator-runtime@".
warning "@storybook/react-native > @storybook/addons > @storybook/api > @reach/[email protected]" has incorrect peer dependency "[email protected] || 16.x || 16.4.0-alpha.0911da3".
warning " > [email protected]" has unmet peer dependency "webpack@>=2".
warning " > [email protected]" has unmet peer dependency "jest-environment-node@>=25.0.0".
warning " > [email protected]" 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(R) Core(TM) 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 `
Using same node/npm version, i am not seeing this issue :/
Maybe a conflict with you having ignite-cli globally installed too, and as such is an old version. Otherwise everything does seem to be building as expected
[03/04/22 1:32PM] ➜ test 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
🏝 Writing your app name in the sand
☕️ Baking CocoaPods
🗄 Backing everything up in source control
[03/04/22 1:32PM] ➜ test npx ignite-cli doctor
System
platform darwin
arch x64
cpu 12 cores Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
directory test /Users/jfulbright/Projects/test
JavaScript (and globally-installed packages)
node 14.17.0 /Users/jfulbright/.nvm/versions/node/v14.17.0/bin/node
npm 6.14.13 /Users/jfulbright/.nvm/versions/node/v14.17.0/bin/npm
npm 6.14.13
yarn 1.22.17
yarn 1.22.17 /Users/jfulbright/.nvm/versions/node/v14.17.0/bin/yarn
create-next-app 12.0.9
create-vite 2.8.0
expo 44.0.6
expo-cli 5.2.0
ngma 1.0.6
serve 13.0.2
surge 0.23.1
pnpm - not installed
Ignite
ignite-cli 7.10.6 /Users/jfulbright/.npm/_npx/29047/bin/ignite
ignite src build /Users/jfulbright/.npm/_npx/29047/lib/node_modules/ignite-cli/build
Android
java 15.0.2 /usr/bin/java
android home - undefined
iOS
xcode 13.2.1
cocoapods 1.11.2 /usr/local/bin/pod
Yeah, I see ignite-cli 3.5.2 in your global packages. Can you run yarn global remove ignite-cli and then try again?
Yeah, I see
ignite-cli 3.5.2in your global packages. Can you runyarn global remove ignite-cliand then try again?
✔ 10065 08:12:16
Thanks. follow your guide, but still throw error
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/26105/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13
throw up;
^
warning expo > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: core-js@<3.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 > [email protected]: 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 > [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
warning react-native > @react-native-community/cli > @react-native-community/cli-plugin-metro > metro > metro-minify-uglify > [email protected]: support for ECMAScript is superseded by uglify-js as of v3.13.0
warning react-native > @react-native-community/cli > @react-native-community/cli-plugin-metro > metro > jest-haste-map > [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: https://github.com/lydell/resolve-url#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: See https://github.com/lydell/source-map-url#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning @storybook/react-native-server > [email protected]: 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 > [email protected]: 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 > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning @storybook/react-native-server > webpack > node-libs-browser > url > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > @storybook/core > webpack-hot-middleware > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > @storybook/ui > @storybook/components > [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
warning @storybook/react-native-server > @storybook/core > react-dev-utils > fork-ts-checker-webpack-plugin > [email protected]: 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 > [email protected]: 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/ui > @storybook/components > react-syntax-highlighter > [email protected]: Support has ended for 9.x series. Upgrade to @latest
warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper > [email protected]: 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 > [email protected]: Version no longer supported. Upgrade to @latest
warning detox > tempfile > [email protected]: 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 > [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
warning solidarity > gluegun > enquirer > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning solidarity > gluegun > prompt-autocompletion > prompt-choices > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning solidarity > gluegun > enquirer > prompt-question > prompt-choices > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning "react-native > react-native-codegen > [email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react@^16.8.1".
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react-native@^0.62.0".
warning " > @rnx-kit/[email protected]" has unmet peer dependency "metro-config@>=0.58.0".
warning "@rnx-kit/metro-config > @rnx-kit/[email protected]" has unmet peer dependency "metro-react-native-babel-preset@".
warning "@storybook/react-native-server > @storybook/[email protected]" has unmet peer dependency "regenerator-runtime@".
warning "@storybook/react-native > @storybook/addons > @storybook/api > @reach/[email protected]" has incorrect peer dependency "[email protected] || 16.x || 16.4.0-alpha.0911da3".
warning " > [email protected]" has unmet peer dependency "webpack@>=2".
warning " > [email protected]" has unmet peer dependency "jest-environment-node@>=25.0.0".
warning " > [email protected]" 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)
dengjianyuan@Jerrys-MacBook-Pro ~ npx ignite-cli doctor
System
platform darwin
arch x64
cpu 12 cores Intel(R) Core(TM) 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
storybook 5.3.19
wml 0.0.83
pnpm - not installed
Ignite
ignite-cli 7.10.6 /Users/dengjianyuan/.npm/_npx/27266/bin/ignite
ignite src build /Users/dengjianyuan/.npm/_npx/27266/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
I am trying to use LTS node, but still throw error
dengjianyuan@Jerrys-MacBook-Pro ~ nvm use 16.14.0
Now using node v16.14.0 (npm v8.3.1)
dengjianyuan@Jerrys-MacBook-Pro ~ npx ignite-cli doctor
Need to install the following packages:
ignite-cli
Ok to proceed? (y) y
System
platform darwin
arch x64
cpu 12 cores Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
directory dengjianyuan /Users/dengjianyuan
JavaScript (and globally-installed packages) node 16.14.0 /Users/dengjianyuan/.nvm/versions/node/v16.14.0/bin/node npm 8.3.1 /Users/dengjianyuan/.nvm/versions/node/v16.14.0/bin/npm corepack 0.10.0 npm 8.3.1 yarn - not installed pnpm - not installed
Ignite ignite-cli 7.10.6 /Users/dengjianyuan/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite ignite src build /Users/dengjianyuan/.npm/_npx/e31027f3785124a8/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 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 npm
█ Bundle identifier: com.MyApp
────────────────────────────────────────────────
🔥 Igniting app
🖨 3D-printing a new React Native app
⠏ Unboxing npm dependencies
/Users/dengjianyuan/.npm/_npx/e31027f3785124a8/node_modules/gluegun/build/index.js:13
throw up;
^
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: 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.
npm WARN deprecated [email protected]: support for ECMAScript is superseded by uglify-js as of v3.13.0
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: Support has ended for 9.x series. Upgrade to @latest
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in: npm ERR! /Users/dengjianyuan/.npm/_logs/2022-03-05T01_02_27_714Z-debug-0.log
(Use node --trace-uncaught ... to show where the exception was thrown)
@jiyuan12354 The last one there shows a Socket Timeout, so thats typically an internet issue or connection problem.
dengjianyuan@Jerrys-MacBook-Pro ~/tmp npx ignite-cli new MyApp ✔ 10977 16:16:17
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·
█ Creating MyApp using Ignite 7.10.8
█ Powered by Infinite Red - https://infinite.red
█ Using ignite-cli with npm
█ Bundle identifier: com.MyApp
────────────────────────────────────────────────
🔥 Igniting app
🖨 3D-printing a new React Native app
⠼ Unboxing npm dependencies
/Users/dengjianyuan/.npm/_npx/e31027f3785124a8/node_modules/gluegun/build/index.js:13
throw up;
^
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN ERESOLVE overriding peer dependency
npm WARN deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: 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.
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated [email protected]: support for ECMAScript is superseded by uglify-js as of v3.13.0
npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated [email protected]: Version no longer supported. Upgrade to @latest
npm WARN deprecated [email protected]: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated [email protected]: core-js@<3.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.
npm ERR! code 1
npm ERR! path /Users/dengjianyuan/tmp/MyApp
npm ERR! command failed
npm ERR! command sh -c node ./bin/postInstall
npm ERR! A complete log of this run can be found in: npm ERR! /Users/dengjianyuan/.npm/_logs/2022-03-25T08_16_23_942Z-debug-0.log
(Use node --trace-uncaught ... to show where the exception was thrown)
npm notice
npm notice New minor version of npm available! 8.3.1 -> 8.5.5
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.5.5
npm notice Run npm install -g [email protected] to update!
npm notice
dengjianyuan@Jerrys-MacBook-Pro ~/tmp npx ignite-cli doctor 1 ↵ 10978 16:19:16 System platform darwin arch x64 cpu 12 cores Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz directory tmp /Users/dengjianyuan/tmp
JavaScript (and globally-installed packages) node 16.14.0 /Users/dengjianyuan/.nvm/versions/node/v16.14.0/bin/node npm 8.3.1 /Users/dengjianyuan/.nvm/versions/node/v16.14.0/bin/npm corepack 0.10.0 npm 8.3.1 yarn - not installed pnpm - not installed
Ignite ignite-cli 7.10.8 /Users/dengjianyuan/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite ignite src build /Users/dengjianyuan/.npm/_npx/e31027f3785124a8/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
Still throw exceptions when initialate project
Hello -- I am getting the same issue when trying to install.
Please help.
I'm not able to reproduce in my environment, so it's difficult to debug. @thecryptocowboy @elirangoshen @jiyuan12354 Can you try running npx ignite-cli new MyApp --debug to see if we can get more of a stacktrace for the error?
I'm not able to reproduce in my environment, so it's difficult to debug. @thecryptocowboy @elirangoshen @jiyuan12354 Can you try running
npx ignite-cli new MyApp --debugto see if we can get more of a stacktrace for the error?
~/tmp/2022 npx ignite-cli new MyApp --debug
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·
█ Creating MyApp using Ignite 7.10.8
█ 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
/Users/dengjianyuan/tmp/2022
/Users/dengjianyuan/tmp/2022/MyApp/.gitignore
/Users/dengjianyuan/.npm/_npx/65727/lib/node_modules/ignite-cli/boilerplate/.gitignore
/Users/dengjianyuan/.npm/_npx/65727/lib/node_modules/ignite-cli/boilerplate/.gitignore.template
⠹ Unboxing npm dependencies yarn install v1.22.10
⠸ Unboxing npm dependencies info No lockfile found.
[1/4] Resolving packages...
⠼ Unboxing npm dependencies [2/4] Fetching packages...
⠏ Unboxing npm dependencies [3/4] Linking dependencies...
⠙ Unboxing npm dependencies [4/4] Building fresh packages...
⠏ Unboxing npm dependencies success Saved lockfile.
$ node ./bin/postInstall
⠼ Unboxing npm dependencies patch-package 6.2.2
Applying patches...
@storybook/[email protected] ✔
⠏ Unboxing npm dependencies
Solidarity checks failed.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
⠋ Unboxing npm dependencies
/Users/dengjianyuan/.npm/_npx/65727/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13
throw up;
^
warning expo > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: core-js@<3.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 > [email protected]: 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-community/cli > @react-native-community/cli-plugin-metro > metro-core > jest-haste-map > [email protected]: 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 > [email protected]: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: https://github.com/lydell/resolve-url#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: See https://github.com/lydell/source-map-url#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning @storybook/react-native-server > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: 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 > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > webpack > node-libs-browser > url > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > @storybook/ui > @storybook/components > [email protected]: 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 > [email protected]: Support has ended for 9.x series. Upgrade to @latest
warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-syntax-highlighter > lowlight > [email protected]: Version no longer supported. Upgrade to @latest
warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper > [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
warning detox > tempfile > [email protected]: 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 > [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
warning solidarity > gluegun > enquirer > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning solidarity > gluegun > enquirer > prompt-question > prompt-choices > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning solidarity > gluegun > prompt-autocompletion > prompt-choices > [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version.
warning "react-native > [email protected]" has incorrect peer dependency "react@^18.0.0".
warning "react-native > react-native-codegen > [email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react@^16.8.1".
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react-native@^0.62.0".
warning " > @rnx-kit/[email protected]" has unmet peer dependency "metro-config@>=0.58.0".
warning "@rnx-kit/metro-config > @rnx-kit/[email protected]" has unmet peer dependency "metro-react-native-babel-preset@*".
warning "@storybook/react-native-server > @storybook/[email protected]" has unmet peer dependency "regenerator-runtime@*".
warning "@storybook/react-native > @storybook/addons > @storybook/api > @reach/[email protected]" has incorrect peer dependency "[email protected] || 16.x || 16.4.0-alpha.0911da3".
warning " > [email protected]" has unmet peer dependency "webpack@>=2".
warning " > [email protected]" has unmet peer dependency "jest-environment-node@>=25.0.0".
warning " > [email protected]" 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)
~/tmp/2022 npx ignite-cli doctor 1 ↵ 10399 09:54:00
System
platform darwin
arch x64
cpu 12 cores Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
directory 2022 /Users/dengjianyuan/tmp/2022
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
storybook 5.3.19
pnpm - not installed
Ignite
ignite-cli 7.10.8 /Users/dengjianyuan/.npm/_npx/67397/bin/ignite
ignite src build /Users/dengjianyuan/.npm/_npx/67397/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
Hello -- I am getting the same issue when trying to install.
Please help.
If you don't care the ignite's version too much, you can try npx [email protected] new MyApp
@jiyuan12354 Thank you! So from that output, it looks like Solidarity is failing and Gluegun is not properly forwarding the error. Can you upgrade Cocoapods to 1.11.2 or higher and try again?
@jiyuan12354 Thank you! So from that output, it looks like Solidarity is failing and Gluegun is not properly forwarding the error. Can you upgrade Cocoapods to 1.11.2 or higher and try again?
still throw error
~/tmp/2022 npx ignite-cli new MyApp --debug ✔ 10703 10:53:49
[object Object]
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·
█ Creating MyApp using Ignite 7.10.8
█ 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
/Users/dengjianyuan/tmp/2022
/Users/dengjianyuan/tmp/2022/MyApp/.gitignore
/Users/dengjianyuan/.npm/_npx/19264/lib/node_modules/ignite-cli/boilerplate/.gitignore
/Users/dengjianyuan/.npm/_npx/19264/lib/node_modules/ignite-cli/boilerplate/.gitignore.template
⠹ Unboxing npm dependencies yarn install v1.22.10
⠸ Unboxing npm dependencies info No lockfile found.
[1/4] Resolving packages...
⠙ Unboxing npm dependencies [2/4] Fetching packages...
⠸ Unboxing npm dependencies [3/4] Linking dependencies...
⠸ Unboxing npm dependencies [4/4] Building fresh packages...
⠴ Unboxing npm dependencies success Saved lockfile.
$ node ./bin/postInstall
⠋ Unboxing npm dependencies patch-package 6.2.2
Applying patches...
@storybook/[email protected] ✔
⠹ Unboxing npm dependencies
✔︎ Solidarity checks valid
⠋ Unboxing npm dependencies Jetifier found 1328 file(s) to forward-jetify. Using 12 workers...
⠧ Unboxing npm dependencies Using Expo modules
⠋ Unboxing npm dependencies Auto-linking React Native modules for target `HelloWorld`: RNCAsyncStorage, RNGestureHandler, RNKeychain, RNScreens, and react-native-safe-area-context
⠹ Unboxing npm dependencies Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
⠸ Unboxing npm dependencies Fetching podspec for `RCT-Folly` from `../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`
⠴ Unboxing npm dependencies Fetching podspec for `boost` from `../node_modules/react-native/third-party-podspecs/boost.podspec`
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
⠧ Unboxing npm dependencies /Users/dengjianyuan/.cocoapods/repos-art/babylon-ios-sdk-cocoapods/.artpodrc
/Users/dengjianyuan/.cocoapods/repos-art/cocoapods-release/.artpodrc
⠼ Unboxing npm dependencies Downloading dependencies
Installing CocoaAsyncSocket (7.6.5)
⠧ Unboxing npm dependencies Installing DoubleConversion (1.1.6)
⠇ Unboxing npm dependencies Installing EXApplication (4.0.2)
Installing EXConstants (13.0.2)
Installing EXErrorRecovery (3.0.5)
Installing EXFileSystem (13.1.4)
Installing EXFont (10.0.5)
Installing EXKeepAwake (10.0.2)
Installing Expo (44.0.6)
Installing ExpoLinearGradient (11.0.3)
Installing ExpoLocalization (12.0.1)
Installing ExpoModulesCore (0.6.5)
Installing FBLazyVector (0.67.2)
Installing FBReactNativeSpec (0.67.2)
⠏ Unboxing npm dependencies Installing Flipper (0.99.0)
⠋ Unboxing npm dependencies Installing Flipper-Boost-iOSX (1.76.0.1.11)
⠹ Unboxing npm dependencies Installing Flipper-DoubleConversion (3.1.7)
⠼ Unboxing npm dependencies Installing Flipper-Fmt (7.1.7)
⠦ Unboxing npm dependencies Installing Flipper-Folly (2.6.7)
⠹ Unboxing npm dependencies Installing Flipper-Glog (0.3.6)
⠇ Unboxing npm dependencies Installing Flipper-PeerTalk (0.0.4)
⠴ Unboxing npm dependencies Installing Flipper-RSocket (1.4.3)
⠴ Unboxing npm dependencies Installing FlipperKit (0.99.0)
⠴ Unboxing npm dependencies Installing OpenSSL-Universal (1.1.180)
⠏ Unboxing npm dependencies Installing RCT-Folly (2021.06.28.00-v2)
⠸ Unboxing npm dependencies Installing RCTRequired (0.67.2)
Installing RCTTypeSafety (0.67.2)
Installing RNCAsyncStorage (1.17.3)
Installing RNGestureHandler (1.10.3)
Installing RNKeychain (6.2.0)
Installing RNScreens (3.8.0)
Installing React (0.67.2)
Installing React-Core (0.67.2)
Installing React-CoreModules (0.67.2)
Installing React-RCTActionSheet (0.67.2)
Installing React-RCTAnimation (0.67.2)
Installing React-RCTBlob (0.67.2)
Installing React-RCTImage (0.67.2)
Installing React-RCTLinking (0.67.2)
Installing React-RCTNetwork (0.67.2)
Installing React-RCTSettings (0.67.2)
Installing React-RCTText (0.67.2)
Installing React-RCTVibration (0.67.2)
Installing React-callinvoker (0.67.2)
Installing React-cxxreact (0.67.2)
Installing React-jsi (0.67.2)
Installing React-jsiexecutor (0.67.2)
Installing React-jsinspector (0.67.2)
Installing React-logger (0.67.2)
Installing React-perflogger (0.67.2)
Installing React-runtimeexecutor (0.67.2)
Installing ReactCommon (0.67.2)
Installing Yoga (1.14.0)
Installing YogaKit (1.18.1)
⠧ Unboxing npm dependencies Installing boost (1.76.0)
⠴ Unboxing npm dependencies Installing fmt (6.2.1)
⠸ Unboxing npm dependencies Installing glog (0.3.5)
⠴ Unboxing npm dependencies Installing libevent (2.1.12)
⠼ Unboxing npm dependencies Installing react-native-safe-area-context (3.1.8)
Generating Pods project
⠧ Unboxing npm dependencies Integrating client project
⠇ Unboxing npm dependencies /Users/dengjianyuan/.cocoapods/repos-art/babylon-ios-sdk-cocoapods/.artpodrc
/Users/dengjianyuan/.cocoapods/repos-art/cocoapods-release/.artpodrc
Pod installation complete! There are 69 dependencies from the Podfile and 59 total pods installed.
⠙ Unboxing npm dependencies Done in 2970.63s.
🧶 Unboxing npm dependencies
⠋ Writing your app name in the sand npx react-native-rename@2 MyApp -b com.MyApp
⠏ Writing your app name in the sand /ios/MyApp RENAMED
Ignore above error if this file doesn't exist
Ignore above error if this file doesn't exist
/ios/MyApp.xcodeproj RENAMED
Ignore above error if this file doesn't exist
/ios/MyApp.xcodeproj/xcshareddata/xcschemes/MyApp.xcscheme RENAMED
/ios/MyAppTests RENAMED
/ios/MyAppTests/MyAppTests.m RENAMED
/ios/MyApp.xcworkspace RENAMED
Ignore above error if this file doesn't exist
/ios/MyApp-Bridging-Header.h RENAMED
/android/app/src/main/res/values/strings.xml MODIFIED
/index.js MODIFIED
/ios/MyApp/Info.plist MODIFIED
/package.json MODIFIED
/app.json MODIFIED
⠦ Writing your app name in the sand /ios/MyApp.xcodeproj/project.pbxproj MODIFIED
⠏ Writing your app name in the sand /ios/MyApp.xcworkspace/contents.xcworkspacedata MODIFIED
⠼ Writing your app name in the sand /ios/MyApp.xcodeproj/xcshareddata/xcschemes/MyApp.xcscheme MODIFIED
⠦ Writing your app name in the sand /ios/MyApp/AppDelegate.m MODIFIED
⠏ Writing your app name in the sand /android/settings.gradle MODIFIED
⠙ Writing your app name in the sand /ios/MyAppTests/MyAppTests.m MODIFIED
⠦ Writing your app name in the sand /ios/Podfile MODIFIED
⠏ Writing your app name in the sand /app.json MODIFIED
android/app/src/main/java/com/myapp BUNDLE IDENTIFIER CHANGED
/android/app/src/main/AndroidManifest.xml MODIFIED
/android/app/BUCK MODIFIED
/android/app/build.gradle MODIFIED
/android/app/src/main/java/com/myapp/MainActivity.java MODIFIED
⠋ Writing your app name in the sand /android/app/src/main/java/com/myapp/MainApplication.java MODIFIED
/android/app/src/main/java/com/myapp/MainActivity.java MODIFIED
android/app/src/debug/java/com/myapp BUNDLE IDENTIFIER CHANGED
/android/app/src/main/AndroidManifest.xml MODIFIED
/android/app/BUCK MODIFIED
/android/app/build.gradle MODIFIED
/android/app/src/debug/java/com/myapp/ReactNativeFlipper.java MODIFIED
⠹ Writing your app name in the sand Done removing builds.
APP SUCCESSFULLY RENAMED TO "MyApp"! 🎉 🎉 🎉
Podfile has been modified, please run "pod install" inside ios directory.
Please make sure to run "watchman watch-del-all" and "npm start --reset-cache" before running the app.
🏝 Writing your app name in the sand
⠙ Baking CocoaPods Scanning for pods...
⠧ Baking CocoaPods 1.11.3
> pod install
⠙ Baking CocoaPods Using Expo modules
⠦ Baking CocoaPods Auto-linking React Native modules for target `MyApp`: RNCAsyncStorage, RNGestureHandler, RNKeychain, RNScreens, and react-native-safe-area-context
⠇ Baking CocoaPods Analyzing dependencies
⠴ Baking CocoaPods /Users/dengjianyuan/.cocoapods/repos-art/babylon-ios-sdk-cocoapods/.artpodrc
/Users/dengjianyuan/.cocoapods/repos-art/cocoapods-release/.artpodrc
⠙ Baking CocoaPods Downloading dependencies
Generating Pods project
⠹ Baking CocoaPods Integrating client project
⠋ Baking CocoaPods /Users/dengjianyuan/.cocoapods/repos-art/babylon-ios-sdk-cocoapods/.artpodrc
/Users/dengjianyuan/.cocoapods/repos-art/cocoapods-release/.artpodrc
Pod installation complete! There are 69 dependencies from the Podfile and 59 total pods installed.
☕️ Baking CocoaPods
/Users/dengjianyuan/.npm/_npx/19264/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13
throw up;
^
yarn run v1.22.10
$ npm-run-all format:* ''
ERROR: Task not found: ""
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
(Use `node --trace-uncaught ...` to show where the exception was thrown)
~/tmp/2022 npx ignite-cli doctor SIGINT(2) ↵ 10705 11:52:19
System
platform darwin
arch x64
cpu 12 cores Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
directory 2022 /Users/dengjianyuan/tmp/2022
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
storybook 5.3.19
pnpm - not installed
Ignite
ignite-cli 7.10.8 /Users/dengjianyuan/.npm/_npx/29458/bin/ignite
ignite src build /Users/dengjianyuan/.npm/_npx/29458/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.3.1
cocoapods 1.11.3 /usr/local/bin/pod
@jamonholmgren is there a way to get Gluegun to tell us more about the error stacktrace?
@robinheinze Hm, I'll have to dig into this at some point. I don't know offhand what's causing it to get swallowed.
Using MacOS if that matters, but even npx [email protected] new MyApp --expo does not work:
🔥 Igniting app
🎫 Cleaning up Expo install
⠏ Unboxing npm dependencies
/.npm/_npx/21977/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13
throw up;
^
npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated [email protected]: core-js@<3.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.
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated [email protected]: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: 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.
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: 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.
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated [email protected]: core-js@<3.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.
npm WARN deprecated [email protected]: support for ECMAScript is superseded by 'uglify-js' as of v3.13.0
+ xcodebuild -version
+ echo 'WARNING: Xcode is not installed on this machine. Skipping iOS framework build phase'
+ exit 0
No patch files found
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node ./bin/postInstall`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /.npm/_logs/2022-04-20T18_39_56_863Z-debug.log
[14:39:56] npm exited with non-zero code: 1
[14:39:56] Error: npm exited with non-zero code: 1
at ChildProcess.completionListener (/.npm/_npx/23531/lib/node_modules/expo-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:65:13)
at Object.onceWrapper (events.js:421:26)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1022:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
...
at Object.spawnAsync [as default] (/.npm/_npx/23531/lib/node_modules/expo-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
at NpmPackageManager._runAsync (/.npm/_npx/23531/lib/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:175:31)
at NpmPackageManager.installAsync (/.npm/_npx/23531/lib/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:91:16)
at NpmPackageManager.addWithParametersAsync (/.npm/_npx/23531/lib/node_modules/expo-cli/node_modules/@expo/package-manager/src/NodePackageManagers.ts:100:36)
at actionAsync (/.npm/_npx/23531/lib/node_modules/expo-cli/src/commands/installAsync.ts:141:24)
(Use `node --trace-uncaught ...` to show where the exception was thrown)`
I see a warning with not having xcode, but did not think that was required to build the app.
I was getting this error but after running yarn global remove ignite-cli and switching to cocoapods 1.11.3 I was successfully able to generate a new ignite project.
Same issue here, debug output as follows
work % npx ignite-cli new MyApp --overwrite --debug
ignite command: /opt/homebrew/Cellar/node/18.5.0/bin/node /opt/homebrew/bin/ignite-cli new MyApp --overwrite --debug
Removing existing project MyApp
[object Object]
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·
█ Creating MyApp using Ignite 7.14.1
█ Powered by Infinite Red - https://infinite.red
█ Using ignite-cli with yarn
█ Bundle identifier: com.myapp
█ Path: /Users/stevebutler/work/MyApp
────────────────────────────────────────────────
🔥 Igniting app
🖨 3D-printing a new React Native app
/Users/stevebutler/work
/Users/stevebutler/work/MyApp/.gitignore
/opt/homebrew/lib/node_modules/ignite-cli/boilerplate/.gitignore
/opt/homebrew/lib/node_modules/ignite-cli/boilerplate/.gitignore.template
⠙ Unboxing npm dependencies yarn install v1.22.0
info No lockfile found.
[1/4] Resolving packages...
⠋ Unboxing npm dependencies [2/4] Fetching packages...
⠼ Unboxing npm dependencies [3/4] Linking dependencies...
⠋ Unboxing npm dependencies [4/4] Building fresh packages...
⠹ Unboxing npm dependencies success Saved lockfile.
$ node ./bin/postInstall
./bin/postInstall script running: npx patch-package
⠧ Unboxing npm dependencies patch-package 6.4.7
Applying patches...
./bin/postInstall script running: pkill -f "cli.js start" || set exit 0
./bin/postInstall script running: jetify
⠼ Unboxing npm dependencies Jetifier found 1468 file(s) to forward-jetify. Using 8 workers...
⠙ Unboxing npm dependencies ./bin/postInstall script running: if [ -d "ios" ]; then cd ios && pod install && cd -; fi
⠹ Unboxing npm dependencies info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
/opt/homebrew/lib/node_modules/ignite-cli/node_modules/gluegun/build/index.js:13
throw up;
^
warning expo > [email protected]: 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 > [email protected]: 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/cli > [email protected]: 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 > [email protected]: 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 > [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
warning react-native > @react-native-community/cli > @react-native-community/cli-plugin-metro > metro > metro-minify-uglify > [email protected]: 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 > [email protected]: https://github.com/lydell/resolve-url#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: See https://github.com/lydell/source-map-url#deprecated
warning react-native > react-native-codegen > jscodeshift > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning @storybook/react-native > @storybook/client-api > [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
warning @storybook/react-native-server > [email protected]: 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 > [email protected]: 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 > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning @storybook/react-native-server > webpack > node-libs-browser > url > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > @storybook/core > webpack-hot-middleware > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @storybook/react-native-server > @storybook/core > react-dev-utils > fork-ts-checker-webpack-plugin > [email protected]: 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 > [email protected]: 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/ui > @storybook/components > [email protected]: 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 > [email protected]: Support has ended for 9.x series. Upgrade to @latest
warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-syntax-highlighter > lowlight > [email protected]: Version no longer supported. Upgrade to @latest
warning @storybook/react-native-server > @storybook/ui > @storybook/components > react-popper-tooltip > react-popper > [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
warning babel-jest > @jest/transform > jest-haste-map > [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
warning detox > tempfile > [email protected]: 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 metro-config > metro > metro-minify-uglify > [email protected]: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
warning mocha > [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
warning mocha > [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react@^16.8.1".
warning "reactotron-react-native > [email protected]" has incorrect peer dependency "react-native@^0.62.0".
warning "@storybook/react-native > @storybook/addons > @storybook/api > @reach/[email protected]" has incorrect peer dependency "[email protected] || 16.x || 16.4.0-alpha.0911da3".
No patch files found
Jetifier is deprecated. Future versions of react-native CLI may not run it by default.
Jetifier: propose an AndroidX conversion PR to this repository: node_modules/detox/android/detox/src/full/java/com/wix/detox/Detox.java
Jetifier: propose an AndroidX conversion PR to this repository: node_modules/detox/android/detox/src/testFull/java/com/wix/invoke/JsonParserTest.java
Jetifier: propose an AndroidX conversion PR to this repository: node_modules/detox/android/detox/src/testFull/java/com/wix/invoke/JsonParserTest.java
/Users/stevebutler/.frum/versions/3.1.2/lib/ruby/3.1.0/rubygems.rb:265:in `find_spec_for_exe': can't find gem cocoapods (>= 0.a) with executable pod (Gem::GemNotFoundException)
from /Users/stevebutler/.frum/versions/3.1.2/lib/ruby/3.1.0/rubygems.rb:284:in `activate_bin_path'
from /usr/local/bin/pod:23:in `<main>'
from /usr/local/bin/ruby_executable_hooks:22:in `eval'
from /usr/local/bin/ruby_executable_hooks:22:in `<main>'
./bin/postInstall failed on command:
if [ -d "ios" ]; then cd ios && pod install && cd -; fi
error Command failed with exit code 1.
(Use `node --trace-uncaught ...` to show where the exception was thrown)
Node.js v18.5.0
Same results running @7.10.2
Edit: noted the above was run against non-LTS node. I've re-tested with LTS and get the same result
Try running
sudo gem install cocoapods
and then doing
pod repo update
and running yarn again in the repo.
Worked for me.
@kentond18 @jiyuan12354 @jeremyspritelyco Have you all tried the latest version of ignite? Solidarity has been removed - see #1968
