-
Notifications
You must be signed in to change notification settings - Fork 1
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
Latest version of webpack emits warnings #5
Comments
Putting "exprContextCritical: false" into the webpack client and server.js appears to work around this problem:
I can run the project with webpack 4.16.5 using this flag. Is this safe enough for production apps until a real fix can be made? Source: https://www.bountysource.com/issues/9623657-critical-dependencies-in-webpack |
@Enalmada, interesting, thank you for the info. For now I will unfreeze the webpack and add this flag with a huge The only worrisome thing is that webpack documentation advises against using of these flags because they are deprecated. Just to clarify: I don't think this boilerplate is ready for any serious production, same as I keep the issue open and it would be great if anyone could shed some more light on this issue and the new workaround. |
I was just lucky enough to stumble upon the huge workaround during some google searching. This issue seems to go into some depth about the problem and might give the experts some idea of what needs to be fixed in the react-universal-component code. |
This is resolved now that we upgraded to |
../node_modules/got/source/request-as-event-emitter.js ../node_modules/keyv/src/index.js Hallo guys, i am trying to fix these 2 errors.. Any solutions;; this is my code use strict'; const EventEmitter = require('events'); const loadStore = opts => { class Keyv extends EventEmitter {
} module.exports = Keyv; |
After upgrading
webpack
to version greater than 4.16.1, the following webpack warnings are emmited during build and hot reloading:For client build:
For server build:
Workaround: downgrade
webpack
to version 4.16.1 (downgraded in current version of the boilerplate)The text was updated successfully, but these errors were encountered: