create-app fails in Node v14.17.0 and then fails to cleanup
See original GitHub issueUsing Node v14.17.0, I tried several times to run npx @backstage/create-app
but each time resulted in a failure to install cypress, and then even though the script announced that it was cleaning up, the app folder was not removed.
Using Node v12.22.1, I was successful.
Expected Behavior
Either app created or folder removed.
Current Behavior
Failed to create app and failed to cleanup.
Possible Solution
Use Node v12.22.1
Steps to Reproduce
npx @backstage/create-app
Your Environment
- macOS BigSur 11.3.1
- node 14.17.0
- yarn 1.22.10
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
create-react-app is not working since version 4.0.1
Use this command to find out if you do: npm list -g --depth 0 . If so, follow the instructions in the error...
Read more >How to fix 'npm does not support Node.js v14' error on ...
My first attempt was updating over the top of my existing node.js installation. I then tried uninstalling node.js installation (Windows Add/ ...
Read more >React Testing Library - npm
Simple and complete React DOM testing utilities that encourage good testing practices.. Latest version: 13.4.0, last published: 4 months ago ...
Read more >Create a Node.js app in the App Engine flexible environment
Clean up. To avoid incurring charges, you can delete your Cloud project to stop billing for all the resources used within that project....
Read more >Release Notes | Firebase - Google
The Firebase Admin Node.js SDK (v11.4.0) is now available. ... This release adds better error messaging for cases when the Emulator UI fails...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Great, please re-open if you encounter the same issue again.
@shoukoo best way for doing a short-term override is often to use Yarn resolutions. You’d add it to the root
package.json
and point it to the version you want. Other options are to add a normal dependency and then twiddle a bit withyarn.lock
to make sure it’s locked to the version you want, or to just modifyyarn.lock
without adding a separate dependency.In this case the release is just about to go out, it’s building atm, so in a couple of minutes you’ll be able to update
@backstage/config-loader
to a version that is compatible with TypeScript 4.3