Skip to content

Conversation

GilbertCherrie
Copy link
Member

Update webpack package versions for webpack, webpack-cli, webpack-dev-server and webpack-stats-plugin

@miq-bot
Copy link
Member

miq-bot commented Jun 18, 2025

Checked commit GilbertCherrie@95b5d9e with ruby 3.1.5, rubocop 1.56.3, haml-lint 0.62.0, and yamllint
0 files checked, 0 offenses detected
Everything looks fine. 🍪

@GilbertCherrie
Copy link
Member Author

GilbertCherrie commented Jul 30, 2025

This pr works but causes terminal to throw this error constantly:

<i> [webpack-dev-server] [HPM] Upgrading to WebSocket
<e> [webpack-dev-server] [HPM] WebSocket error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
<e>     at _write (node:internal/streams/writable:489:11)
<e>     at Writable.write (node:internal/streams/writable:510:10)
<e>     at Sender.sendFrame (/Users/gilbertcherrie/manageiq-ui-service/node_modules/webpack-dev-server/node_modules/ws/lib/sender.js:561:20)
<e>     at Sender.close (/Users/gilbertcherrie/manageiq-ui-service/node_modules/webpack-dev-server/node_modules/ws/lib/sender.js:222:12)
<e>     at WebSocket.close (/Users/gilbertcherrie/manageiq-ui-service/node_modules/webpack-dev-server/node_modules/ws/lib/websocket.js:315:18)
<e>     at Receiver.receiverOnConclude (/Users/gilbertcherrie/manageiq-ui-service/node_modules/webpack-dev-server/node_modules/ws/lib/websocket.js:1162:18)
<e>     at Receiver.emit (node:events:524:28)
<e>     at Receiver.controlMessage (/Users/gilbertcherrie/manageiq-ui-service/node_modules/webpack-dev-server/node_modules/ws/lib/receiver.js:658:14)
<e>     at Receiver.getData (/Users/gilbertcherrie/manageiq-ui-service/node_modules/webpack-dev-server/node_modules/ws/lib/receiver.js:477:12)
<e>     at Receiver.startLoop (/Users/gilbertcherrie/manageiq-ui-service/node_modules/webpack-dev-server/node_modules/ws/lib/receiver.js:167:16) {
<e>   code: 'ERR_STREAM_WRITE_AFTER_END'
<e> }

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

Successfully merging this pull request may close these issues.

3 participants