tiagocoutinho / multivisor

Centralized supervisor WebUI and CLI
GNU General Public License v3.0
184 stars 37 forks source link

missing/conflicting development dependencies #81

Open cathaychris opened 2 years ago

cathaychris commented 2 years ago

I'd like to play around with developing the frontend for a custom application.

However, following the readme and installing in an environment usingnpm at 7.24.2 and node at 14.18.0 produces conflicts with the development dependencies. In particular, with webpack-dev-server, which at ^3.1.14 requires webpack-cli at ^3.1.0, which is not locked in package-lock.json or referenced in package.json or anywhere in this repository. (Technically, webpack-cli also requires webpack>4, which is pinned to ^3.12.0 in this repository.)

Without webpack-cli, trying to run npm run dev and thereby webpack-dev-server will throw an error requesting the CLI, https://github.com/webpack/webpack-dev-server/blob/v3.1.14/bin/webpack-dev-server.js#L71.

Installing a later webpack (>=4) results in a completely different syntax for the webpack config file, so that's clearly now how this repo has been developed in this snapshot.

Installing webpack-cli at 3.1.0 and ignoring peer dependencies (to avoid the webpack>4 requirement) and running webpack gives an obscure error, TypeError: Cannot destructure property 'compile' of 'compiler.hooks' as it is undefined. Probably there is a version conflict, somewhere. Other versions of the CLI produce different errors.

It would be helpful if anybody with a working development environment could share the environment specifics and resolutions to the missing and conflicting dependencies.