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
WARNING in ./node_modules/ws/lib/BufferUtil.js on using of Websocket in storybook #1236
Comments
Duplicate of #1220. See discussion there. |
but this is not in webpack this in storybook |
Those warnings are created by webpack which is used by storybook. If you are using |
What's the recommendation for learning WebSockets? |
Closing as there is not much we can do about this. |
That's not a real warning! You can forget it |
hi, i am using websocket in my config file but after usage of websocket i am getting warnings like that
`
WARNING in ./node_modules/ws/lib/BufferUtil.js
Module not found: Error: Can't resolve 'bufferutil' in '/home/waheed/Projects/Components/node_modules/ws/lib'
@ ./node_modules/ws/lib/BufferUtil.js 35:21-42
@ ./node_modules/ws/lib/PerMessageDeflate.js
@ ./node_modules/ws/lib/WebSocketServer.js
@ ./node_modules/ws/index.js
@ ./dev/client.js
@ ./.storybook/config.js
@ multi ./node_modules/@storybook/react/dist/server/config/polyfills.js ./node_modules/@storybook/react/dist/server/config/globals.js (webpack)-hot-middleware/client.js?reload=true ./.storybook/config.js
WARNING in ./node_modules/ws/lib/Validation.js
Module not found: Error: Can't resolve 'utf-8-validate' in '/home/waheed/Projects/Components/node_modules/ws/lib'
@ ./node_modules/ws/lib/Validation.js 10:22-47
@ ./node_modules/ws/lib/Receiver.js
@ ./node_modules/ws/index.js
@ ./dev/client.js
@ ./.storybook/config.js
@ multi ./node_modules/@storybook/react/dist/server/config/polyfills.js ./node_modules/@storybook/react/dist/server/config/globals.js (webpack)-hot-middleware/client.js?reload=true
./.storybook/config.js
`
i just want to remove these warnings on my console .how can i remove these warnings.
The text was updated successfully, but these errors were encountered: