-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Webpack 5 #57
Comments
For those wanting to use this package with Webpack 5, here's a way to do so:
module: {
...
},
resolve: {
...,
extensions: ['*', '.js', '.jsx'],
fallback: {
'util': require.resolve('util/')
}
},
plugins: {
...,
new webpack.ProvidePlugin({
// Make a global `process` variable that points to the `process` package,
// because the `util` package expects there to be a global variable named `process`.
// Thanks to https://stackoverflow.com/a/65018686/14239942
process: 'process/browser'
})
} |
Updating the docs so webpack 5 users can reverse v5’s breakage sounds like a good idea. |
Ya, that's what I'm thinking, too. Especially once Webpack 5 becomes the norm, although at the moment I think Webpack 4 is still far more popular 🙂 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@Bosch-Eli-Black
|
websocket connection closed with code: 1006 |
@QGB Please file new bugs for these 🙂 |
@QGB Instructions for how to fix that error are in the error message 😉
|
Ref browserify/node-util#57 (comment) Signed-off-by: Richard Steinmetz <[email protected]>
Ref browserify/node-util#57 (comment) Signed-off-by: Richard Steinmetz <[email protected]>
FYI, my understanding is that Webpack 5 does not automatically include this package by default, so this package's documentation may need to be updated 🙂
The text was updated successfully, but these errors were encountered: