Skip to content
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

Uncaught Error: Cannot find module './log' #1049

Closed
johan-lejdung opened this issue Aug 22, 2017 · 1 comment
Closed

Uncaught Error: Cannot find module './log' #1049

johan-lejdung opened this issue Aug 22, 2017 · 1 comment

Comments

@johan-lejdung
Copy link
Contributor

What is the current behavior?
We recieve a warning in the console:

Uncaught Error: Cannot find module './log'.
    at webpackContextResolve (bundle.js:84181)
    at webpackContext (bundle.js:84176)
    at Object.log-level (bundle.js:78566)
    at SockJS.sock.onmessage (bundle.js:80519)
    at SockJS.EventTarget.dispatchEvent (bundle.js:43017)
    at bundle.js:82337
    at Array.forEach (<anonymous>)
    at SockJS._transportMessage (bundle.js:82335)
    at WebSocketTransport.EventEmitter.emit (bundle.js:3748)
    at WebSocketTransport.ws.onmessage (bundle.js:80623)

What is the expected behavior?
No Warning, we are not using hot-reloading.

What we think is happening
The warning is generated from this line. We are not using hot-reloading but it looks like the code think we are.

If we call hotCtx.keys() on line 80 in the commit above we get this array:

["../package.json", "./console", "./formatters"]

Please mention your webpack and Operating System version.
MacOs Sierra
Webpack-dev-server: 2.7.1
Webpack: 3.5.5

@johan-lejdung
Copy link
Contributor Author

PR here: #1050

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant