npx ignite-cli new fails #2564
Comments
|
I have reproduced, thank you |
|
@lkc-csu so you're unblocked, can you replace your
|
|
hi frank,
thanks a lot. i seriously thought this was my problem. i won’t be able to try out the new tsconfig.json file until tomorrow.
lee
On Nov 20, 2023, at 4:34 PM, Frank Calise ***@***.******@***.***>> wrote:
** Caution: EXTERNAL Sender **
@lkc-csu<https://github.com/lkc-csu> so you're unblocked, can you replace your tsconfig.json with the following and see if you can get up and running?
{
"compilerOptions": {
"allowJs": false,
"allowSyntheticDefaultImports": true,
"esModuleInterop": true,
"experimentalDecorators": true,
"jsx": "react-native",
"module": "es2015",
"moduleResolution": "node",
"strict": true,
"noEmit": true,
"noImplicitAny": true,
"noImplicitReturns": true,
"noImplicitThis": true,
"noUnusedLocals": true,
"sourceMap": true,
"target": "ESNext",
"lib": ["DOM", "ESNext"],
"skipLibCheck": true,
"resolveJsonModule": true,
"baseUrl": ".",
"paths": {
"app/*": ["./app/*"],
"assets/*": ["./assets/*"]
}
},
"ts-node": {
"compilerOptions": {
// compilerOptions specified here will override those declared above,
// but *only* in ts-node. Useful if you want ts-node and tsc to use
// different options with a single tsconfig.json.
"module": "commonjs"
}
},
"include": ["App.tsx", "app", "types", "plugins", "app.config.ts"],
"exclude": ["node_modules", "test/**/*"]
}
—
Reply to this email directly, view it on GitHub<#2564 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFOMNCBRRU42YZFMC3A3METYFPSJLAVCNFSM6AAAAAA7TQGPZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJZHE3TIMZYGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
lee casuto
***@***.******@***.***>
|
|
I had the same error today trying to set up a new app. I tried your suggested tsconfig.json, but it did not like --prebuild. Perhaps you meant "prebuild" without the dashes: npx expo prebuild --clean. (I am new to Expo, sorry.) That seemed to work, although it warned me that "We couldn't find a git repository in your project directory. It's recommended to back up your project before proceeding." Is the git repo initialization the only thing that is missing by using this workaround? (App seemed to build and run fine, using npx expo run:ios... but I am concerned if there were any other steps missed by Ignite? I would hate to start putting a lot of time into this to only have to wait and redo everything when a proper fix is released.) I am really excited to start using v9. Thanks! |
|
Related to TypeStrong/ts-node#2076 (comment) Will lock down the TS version for now until it's fixed |
|
@tlv-developer yeah I understand the concern. You could also spin up an Ignite app via Expo Go (which won't run prebuild), this will finish with all the proper steps (git repo initilization, etc). Then either modify the The PR is up for the same fix, just waiting on review. |
|
@tlv-developer give |
|
Same here. I updated and it broke so I made a new project and it failed as well. This happened of Expo Go too. Ignite version9.0.0 Additional info@frankcalise 's solution worked fine. |
|
@onurusluca Did you change the TypeScript dependency to "5.2.2" and reinstall deps before running prebuild? Please copy your package json here. You'll have to do this if you continue to use 9.0.0 or 9.0.1 until the fix is live Or you can just try |
I just did an update and it broke. I checked, it updated package.json(after update): |
|
@onurusluca |
That did it! Working flawlessly. |
|
same issue for a first time user. I wanted to try out ignite and I get this error. I even tried the DYI option it still didn't work out. I tried both latest and ignite-cli@next options for the cli. With the next version it indeed puts the 5.2.2 version without the ^ but still throws same error. tsconfig.json What I noticed is that it tries to extend the expo/tsconfig but there is no expo folder created in the project. |
|
@maxbureac it comes from node_modules, can you provide |
|
just throws an error btw running it with yarn dlx instead of npx because of yarn berry |
|
@maxbureac yarn 2/3 has issues #2518 you can try another package manager for now via |
|
Only during setup or in general? |
|
@maxbureac expo/expo-cli#1073 not sure it'll be supported - but have you created expo apps with the same yarn version without issue? if so you could run your ignite new command with |
|
@frankcalise I don't use expo cli. This was another weird thing that I was doing the manual workflow but it still referenced expo stuff. |
|
🎉 This issue has been resolved in version 9.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
the command:
npx ***@***.*** new PizzaApp
works perfectly. now i just wish i did (half as well as you) thank you so much.
lee
On Nov 21, 2023, at 8:44 AM, Frank Calise ***@***.******@***.***>> wrote:
** Caution: EXTERNAL Sender **
Closed #2564<#2564> as completed via #2565<#2565>.
—
Reply to this email directly, view it on GitHub<#2564 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFOMNCCHV6LM2M5YC4KIVEDYFTD7XAVCNFSM6AAAAAA7TQGPZWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGAZDMMJWGE3DONQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
lee casuto
***@***.******@***.***>
|
|
@lkc-csu you're quite welcome, |
|
Appreciate everyone reporting this issue and kudos to @frankcalise for finding the fix! |
|
absolutely!
On Nov 21, 2023, at 11:14 AM, Jamon Holmgren ***@***.******@***.***>> wrote:
** Caution: EXTERNAL Sender **
Appreciate everyone reporting this issue and kudos to @frankcalise<https://github.com/frankcalise> for finding the fix!
—
Reply to this email directly, view it on GitHub<#2564 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFOMNCACIBOYUK2XOTRUBH3YFTVPVAVCNFSM6AAAAAA7TQGPZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRRGQZDEMRRGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
lee casuto
***@***.******@***.***>
|
Describe the bug
The following error occurred:
i'm quite willing to believe it is me and not the software. but thanks.
The text was updated successfully, but these errors were encountered: