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.
Current CRA install is incompatible with 1.0
See original GitHub issueI wanted to open this to make sure we’re tracking this issue and handle it through documentation in some way. As noted in #909, the current version of CRA targets typescript: ~3.7.2, which is not recent enough to be compatible with Chakra (which takes advantage of the import type/export type syntax from 3.8).
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
create-react-app dependency version issues with React 18
Here is a temporary workaround: Install cra-template to a separate folder (other than your new project app's folder) using "npm install cra- ...
Read more >Fix list for IBM WebSphere Application Server V8.5
IBM WebSphere Application Server provides periodic fixes for the base and Network Deployment editions of release V8.5. The following is a complete listing ......
Read more >node sass version 6.0.1 is incompatible with ^4.0.0 - You.com
Workaround: don't install node-sass 5.0.0 yet (the major version was just bumped). Uninstall node-sass. npm uninstall node-sass. Then install the latest version ...
Read more >Upgrade Guide - Tailwind CSS
Update Tailwind and install PostCSS and autoprefixer using npm: ... The @tailwindcss/custom-forms plugin is not compatible with Tailwind CSS v2.0.
Read more >Releases - styled-components
Updating styled components is usually as simple as npm install . ... update react-native component aliases to current stable list ... v5.1.0 ......
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
This is being held up by a last-minute CRA change to service workers, and we hope to have this out in the coming days… but can’t promise. Sorry all.
Hi @with-heart, I can tell you that we’re very close to releasing a new version of CRA, so that should solve the issue.
In the meantime, CRA users can definitely bump their TS version with no issue (although they might find that the included ESLint config doesn’t support the new syntax).