-
-
Notifications
You must be signed in to change notification settings - Fork 27k
react-scripts-build => 'navigator is not defined' #1875
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
Comments
Remove the line https://github.com/ztotta/Portfolio/blob/e7ec3e6abc19bb9f6761aa755287b4db0d8aa195/src/App.css#L162 (App.css:162) There is an empty URL which is trying to be resolved. I agree though, the error is quite cryptic. |
Thank you!!! |
Wow, that error is super confusing. |
Tagging as up for grabs. The follow up item here is to create a minimal reproducing case with just Webpack (no CRA) and file a bug in the appropriate project (it's likely either |
Ok finally found out what the problem is. Webpack is trying to load It's quite weird that Webpack actually executes the code inside the files. You can also see If you change import './App.css';
console.log('========= Oopsie! !========');
require('react-responsive-sidebar'); This obscure behaviour when importing |
So what is the next step here? Is this supposed to be fixed in Webpack? Should we file another issue? |
Thought this issue was fixed for Webpack ^2.1.0 but apparently this is only fixed for specific webpack/webpack#4541 This is a repo that reproduces these issues: |
Cool, I'll close our issue then. Thanks for following up. |
Attempting to build & deploy to gh-pages, but it's failing at 'react-scripts-build', throwing 'Module build failed: ReferenceError: navigator is not defined'. It appears to be coming from App.css, but I can't find what 'navigator' is referring to in the first place. Do you know what 'navigator' refers to and what could be causing this?
Here's the commit of the project at this point: ztotta/zach_totta@e7ec3e6
And here's the log:
The text was updated successfully, but these errors were encountered: