Dependency Use force update 1.0.10 causes a Type Error
See original GitHub issueIt seems that the dependency ‘use-force-update 1.0.10’ throws a Type error when using the useGlobal
hook:
Uncaught TypeError: use_force_update_1.default is not a function
Rolling back to use-force-update v1.0.8 fixes the issue.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
npm install didn't update the dependencies - Stack Overflow
You need to install react-native-cli first using npm install -g react-native-cli. Then try npm install. delete package-lock.json file and node ...
Read more >CRA5 Bug: require a submodule of a package (ie my ... - GitHub
An app created using yarn create react-app that shows the issue: ... Dependency Use force update 1.0.10 causes a Type Error ...
Read more >use-force-update - npm
use -force-update. TypeScript icon, indicating that this package has built-in type declarations. 1.0.11 • Public • Published 23 days ago.
Read more >History | Poetry - Python dependency management and ...
ParseConstraintError is now raised on version and constraint parsing errors, and includes information on the package that caused the error (#514).
Read more >Important notes — Borg - Deduplicating Archiver 1.2.2 ...
Although borg uses the hashtables very heavily, the index corruption did not ... clarify pp vs. pf pattern type, #5300; update referenced freebsd/macOS ......
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
I’m able to reproduce this. The
use-force-update
import is being returned by Webpack as a string (/path/to/some-file.cjs
) instead of returning the actual module.There is a bug report for this at facebook/create-react-app#11889 and a pull request to fix it at #12352.
Here are some solutions:
react-scripts
to^4
until they resolve it in^5
.use-force-update
to1.0.8
.react-scripts
and update your Webpack config like this.react-scripts
.The easiest solution is likely to downgrade
react-scripts
. If you want the newest toys (who doesn’t?), then lockinguse-force-update
at1.0.8
should work. It may be hard to patch your lock file manually, so depending on your package manager you can check out alternatives.For NPM v8+:
For Yarn1:
For Yarn2:
The third best solution is probably CRACO, because it’s easy to just delete the CRACO config file if you decide you don’t want it anymore. It’s also nice to just have that freedom to configure Webpack regardless.
I hope one of these work for you. I could “fix” it in the package itself, but that would require removing native ESM support, and I’m reluctant to think that to be the right choice. 😞
I’ll look into this. Can you confirm if you are using React Native or is this a browser project?