npm install errors regarding webpack/webpack-stream

[dmoebius]

Your issue may already be reported! Please search on the issue track before creating one.

• [ ] Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
• [x] Are you running the latest version?
• [x] Are you reporting to the correct repository?

Bug Report

Environment

• Bulma version: 6.1.19
• OS: any, Arch Linux in my case
• Node.js 20.5.0
• npm 9.8.1

Current Behavior Trying to build bulma-calender manually.

npm install gives the following errors:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: webpack-stream@7.0.0
npm ERR! Found: webpack@4.46.0
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"^4.12.0" from the root project
npm ERR!   peer webpack@"2 || 3 || 4" from babel-loader@7.1.5
npm ERR!   node_modules/babel-loader
npm ERR!     dev babel-loader@"^7.1.4" from the root project
npm ERR!   1 more (terser-webpack-plugin)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.21.2" from webpack-stream@7.0.0
npm ERR! node_modules/webpack-stream
npm ERR!   dev webpack-stream@"^7.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@5.88.2
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^5.21.2" from webpack-stream@7.0.0
npm ERR!   node_modules/webpack-stream
npm ERR!     dev webpack-stream@"^7.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Possible Solution Running with npm install --legacy-peer-deps works, but I don't know what this does, and if it has any drawbacks.