ignite
ignite copied to clipboard
Getting all files names as Hello World after creating new app
Describe the bug
I have created new app using this command npx ignite-cli new MyAwesomeApp
.
Main folder is named correctly but files inside android and ios folders have HelloWorld in it. I don't know where this is coming from as all these files should be named on my project name.
I am expecting all files to be named with real project name and not like HelloWold
Here I have attached screenshots of some of the files
Ignite version
7.15.0
Additional info
System
platform darwin
arch x64
cpu 4 cores Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
directory cheetah /Users/cheetah
JavaScript (and globally-installed packages)
node 16.8.0 /usr/local/bin/node
npm 8.5.1 /usr/local/bin/npm
@aws-amplify/cli 7.6.21
npm 8.5.1
react-native-cli 2.0.1
typescript 4.2.4
yarn 1.22.10
yarn 1.22.10 /usr/local/bin/yarn
pnpm - not installed
expo - not installed
Ignite
ignite-cli 7.15.0 /Users/cheetah/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src build /Users/cheetah/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java 1.8.0_292 /usr/bin/java
android home - /Users/cheetah/Library/Android/sdk
iOS
xcode 13.3.1
cocoapods 1.11.0 /usr/local/bin/pod
Thank for submitting this @MuhammadAbdullah54321
The Ignite team is working towards a new major release we are calling Ignite Maverick. The beta is live now, and I suspect it will solve your issue.
You can try it today with
npx ignite-cli@next new
Thanks for prompt response
Also I just want to mention that when I run this command npx ignite-cli new MyAwesomeApp
to create a new project .... It's very slow and takes hours and hours stuck on this screen.
I have attached screenshot below

Yes, unfortunately react-native projects like Ignite have a lot of node_modules
dependencies, and it is quite heavy. How is your internet connection? I have issues with the unboxing npm dependencies step when I am on slow or unreliable connections.
I would also recommend trying to run the command without installing dependencies. Ignite Maverick will allow you to do so with the following flag
npx ignite-cli@next new MyAwesomeApp --install-deps=false
My internet connection is fair enough ... not very slow.
if I use this flag --install-deps=false
, will I be able to later install them using yarn
command ?
Yes, absolutely!
I tried the new command npx ignite-cli@next new
you mentioned above
And the issue of my files being named as HelloWorld is still not solved.
Here is the terminal output:
/Users/cheetah/.npm/_npx/2351a7c35afcf833/node_modules/gluegun/build/index.js:15
throw up;
^
warning @expo/webpack-config > webpack-dev-server > [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning @expo/webpack-config > webpack-dev-server > chokidar > [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
warning @expo/webpack-config > webpack-dev-server > sockjs > [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/webpack-config > webpack-dev-server > 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 @expo/webpack-config > webpack-dev-server > url > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning @expo/webpack-config > webpack > watchpack > watchpack-chokidar2 > [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning @expo/webpack-config > webpack > micromatch > snapdragon > [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
warning @expo/webpack-config > webpack > micromatch > snapdragon > source-map-resolve > [email protected]: https://github.com/lydell/resolve-url#deprecated
warning @expo/webpack-config > webpack > micromatch > snapdragon > source-map-resolve > [email protected]: See https://github.com/lydell/source-map-url#deprecated
warning @expo/webpack-config > webpack > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://github.com/lydell/urix#deprecated
warning @expo/webpack-config > optimize-css-assets-webpack-plugin > cssnano > cssnano-preset-default > postcss-svgo > [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
warning @expo/webpack-config > optimize-css-assets-webpack-plugin > cssnano > cssnano-preset-default > postcss-svgo > svgo > [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 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 > @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 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 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 detox-expo-helpers > xdl > [email protected]: Beta version should not be used anymore
warning detox-expo-helpers > xdl > [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).
warning detox-expo-helpers > xdl > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning detox-expo-helpers > xdl > [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 detox-expo-helpers > xdl > @expo/bunyan > [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 detox-expo-helpers > xdl > [email protected]: Please upgrade to @sentry/node. See the migration guide https://bit.ly/3ybOlo7
warning detox-expo-helpers > xdl > raven > [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 detox-expo-helpers > xdl > @expo/ngrok > [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 detox-expo-helpers > xdl > [email protected]: Please upgrade to @sentry/browser. See the migration guide https://bit.ly/3ybOlo7
warning detox-expo-helpers > xdl > [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
warning detox-expo-helpers > xdl > @expo/ngrok > [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
warning detox-expo-helpers > xdl > request > [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 detox-expo-helpers > xdl > [email protected]: Deprecated due to CVE-2021-21366 resolved in 0.5.0
warning detox-expo-helpers > xdl > plist > [email protected]: Deprecated due to CVE-2021-21366 resolved in 0.5.0
warning detox-expo-helpers > xdl > joi > [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.
warning detox-expo-helpers > xdl > [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
warning detox-expo-helpers > xdl > slugid > [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 detox-expo-helpers > xdl > analytics-node > [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.
warning detox-expo-helpers > xdl > joi > [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.
warning detox-expo-helpers > xdl > joi > topo > [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.
warning detox-expo-helpers > xdl > request > [email protected]: this library is no longer supported
warning detox-expo-helpers > xdl > @expo/osascript > babel-runtime > [email protected]: core-js@<3.23.3 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. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning detox-expo-helpers > xdl > analytics-node > superagent > [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
warning detox-expo-helpers > xdl > pacote > make-fetch-happen > [email protected]: This module is not used anymore, npm uses minipass-fetch for its fetch implementation now
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".
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
Ignoring ffi-1.15.0 because its extensions are not built. Try: gem pristine ffi --version 1.15.0
[!] The version of CocoaPods used to generate the lockfile (1.11.3) is higher than the version of the current executable (1.11.0). Incompatibility issues may arise.
./bin/postInstall failed on command:
if [ -d "ios" ]; then cd ios && pod install && cd -; fi
error Command failed with exit code 31.
(Use node --trace-uncaught ...
to show where the exception was thrown)
So I tried this ...
I ran this command npx ignite-cli@next new MyAwesomeProject
and choose the option to NOT install the dependencies.
Now not only new project setup was completed much faster but also this time my issue is solved. Now all my files inside iOS and Android folders are named on MyAwesomeProject and not on Hello World
Later I installed my deps using yarn
and everything now works fine
So it seems like issue happens while installing deps
I'm going to close this issue for now, since we have found a workflow that is working for you. Feel free to re-open this if you are running into more issues with it