-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2 error: "Uncaught ReferenceError: exports is not defined" when using react-scripts v5 #23
Comments
I've reported this bug in the create-react-app issue tracker facebook/create-react-app#11898 |
work around (sort of)If you are having this error, you need to downgrade to react-scripts v4
You then need to follow the steps outlined in this comment: Note: eslint needs to be installed as Once all that is done, close and re-open your editor. |
I'm happy to help take a look here @Dan503 (this looks like affecting more than just react-scripts projects, but likely a number of people using webpack 5). I went to go try a few fixes that may work, but cannot seem to get the base project as it stands to build. Wondering if you can help me get set up and then I'm happy to take a look!? |
I can't do it tonight but I'll try and see if I can get it working tomorrow night. I haven't worked on this for a long time now. |
@agrohs have you tried installing using |
Thanks @Dan503, I haven't run that command specifically, but I'm pretty deep into updating things at this point to get this to work. I have a fork w/ a few branches I'm working through (had to fork and fix packaging for both the react project as well as the core utils project). I finally have everything compiling and all cypress tests passing (containing output that does not cause the If you happen to have any time free anywhere in next few days, let me know and happy to connect over email/zoom/whatever and perhaps work through together. I'm close, but I've also been spinning on some small things for hours that I'm sure you'd know right away offhand |
@agrohs are you available now or within the next couple hours? I have some time to work on the project now. |
@agrohs it seems like my night time is impractical for you. I'll be available Saturday morning (Sydney time GMT +11) |
Hello @Dan503 - just saw this (apologies on missing the notification earlier), but happy to fine something that works across timezones. Let me see if I can catch you on Twitter/LinkedIn/trade some emails/DMs and we can connect from there! (I have made pretty solid progress on this and know what the cause is it least - and have a fix for it - but encountered a handful of other things on top I started spinning on) |
@agrohs I've got an update on this. I have a working version on this branch: 2 of the unit tests are failing because the keydown command isn't updating the state fast enough for the test to pass. It doesn't seem to update the state until either it starts rapidly firing keydown events or the keyup event is triggered. I can probably still publish while ignoring this failed test but I'd rather not have a failing test if I can avoid it. I haven't tested in IE11 yet but the error mentioned in the issue isn't present anymore. |
I've published the version associated with that branch as v2.0.3-beta.0 so it can be npm installed using the @beta tag |
I installed this into a simple CRA project that has these dependencies:
I think the main issue is the upgrade from react-scripts v4 to v5.
It is giving me this error:
Repository demonstrating the error:
https://github.com/Dan503/time-input-polyfill-tests/tree/react-version
I can't figure out what the issue is :(
The text was updated successfully, but these errors were encountered: