Dependency Use force update 1.0.10 causes a Type Error #227

Activity

1. quisido commented on Aug 11, 2022

   

   quisido

   on Aug 11, 2022

   Collaborator

   More actions

   I'll look into this. Can you confirm if you are using React Native or is this a browser project?

   👍React with 👍1Reacted by Ngô Xuân Bách
2. jessesward commented on Aug 12, 2022

   

   jessesward

   on Aug 12, 2022

   Author

   More actions

   I'll look into this. Can you confirm if you are using React Native or is this a browser project?

   This is a browser project. Using React v18.2.0
3. ngobach commented on Aug 12, 2022

   

   ngobach

   on Aug 12, 2022

   More actions

   It is reproducible with react-scripts@^5.
4. quisido commented on Aug 12, 2022

   

   quisido

   on Aug 12, 2022

   Collaborator

   More actions

   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:

   • Downgrade react-scripts to ^4 until they resolve it in ^5.
   • Downgrade use-force-update to 1.0.8.
   • Install Craco and use this configuration.
   • Eject from react-scripts and update your Webpack config like this.
   • Use the commit in the pull request for your copy of react-scripts.

   The easiest solution is likely to downgrade react-scripts. If you want the newest toys (who doesn't?), then locking use-force-update at 1.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+:

   package.json
   {
     "overrides": {
       "use-force-update": "1.0.8"
     }
   }
   

   For Yarn1:

   package.json
   {
     "resolutions": {
       "use-force-update": "1.0.8"
     }
   }
   

   For Yarn2:

   # .yarnrc.yml
   packageExtensions:
     'reactn@*':
       dependencies:
         use-force-update: 1.0.8

   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. 😞

   👍React with 👍3Reacted by Ryan Jentzsch, Hazem Taha and Mitch Downey
5. jessesward commented on Aug 13, 2022

   

   jessesward

   on Aug 13, 2022

   Last edited by jessesward

   Author

   More actions

   Thanks for looking into it!

   For now I think I'll just lock use-force-update to 1.0.8. Seems to be the best option. Hopefully the webpack issue will get worked out soon.
6. ngobach commented on Aug 13, 2022

   

   ngobach

   on Aug 13, 2022

   More actions

   I was upgrading react-scripts from ^4 to ^5 and use-force-update is the only library that broke the build. So I guess this library might be using something non-standard. I found this exports interesting but it could be the reason of breaking changes (from ^1.0.8).

   {
     "exports": {
       ".": {
         "import": "./dist/esm/index.js",
         "require": "./dist/cjs/index.cjs"
       }
     }
   }
   
7. quisido commented on Aug 13, 2022

   

   quisido

   on Aug 13, 2022

   Collaborator

   More actions

   The reason is the cjs file extension, which is standard in newer versions of Node for packages that contain both CJS and ESM code. Others are experiencing it for other dependencies in the CRA bug report linked above.

   It's true that not many dependencies use the CJS file extension. Not many dependencies vend both CJS and ESM builds.
8. RyanNerd

   added a commit that references this issue on Aug 19, 2022

   🐛 bug Downgrade `react-scripts` to ^4.0.3

   ...

   beaf58e
9. mitchdowney

   added a commit that references this issue on Jan 12, 2023

   Fix module error with reactn and use-force-update by setting resoluti…

   ...

   057ce56