new aegir always gives scary error #204
Assignees
Comments
|
Are you scared about the |
|
ahah I'm not "scared" :P, but it does print a ton of stuff for just not finding a browser.js (all of those lines are printed just because one file is not found). |
vmx
added a commit
that referenced
this issue
Mar 12, 2018
Check if `test/browser.js` exist before webpack is initiated and require it only if it really exist. This makes a warning go away that lead to a lot of console output. Fixes #204.
vmx
added a commit
that referenced
this issue
Mar 12, 2018
Check if `test/browser.js` exist before webpack is initiated and require it only if it really exist. This makes a warning go away that lead to a lot of console output. Fixes #204.
vmx
added a commit
that referenced
this issue
Mar 28, 2018
Check if `test/browser.js` exist before webpack is initiated and require it only if it really exist. This makes a warning go away that lead to a lot of console output. Fixes #204.
vmx
added a commit
that referenced
this issue
Mar 28, 2018
Check if `test/browser.js` exist before webpack is initiated and require it only if it really exist. This makes a warning go away that lead to a lot of console output. Fixes #204.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can this be improved? //cc @vmx
It happens in modules that have no
browser.jsfile.The text was updated successfully, but these errors were encountered: