While attempting to contribute I noticed that the npm version used to generate the package lock is really out of date. Furthermore, the packages from @moxy despite having the same version number, depend on different minimum versions of eslint making it difficult to upgrade using npm.
Upon attempting to install npm packages on the latest version I get lots of peer dependency conflicts that are impossible to resolve. I had to use the --legacy-peer-deps option to successfully install.
I would have a go myself, but I'm unsure of whether there are any conscious decisions to have the current set up.
While attempting to contribute I noticed that the npm version used to generate the package lock is really out of date. Furthermore, the packages from @moxy despite having the same version number, depend on different minimum versions of eslint making it difficult to upgrade using npm.
Upon attempting to install npm packages on the latest version I get lots of peer dependency conflicts that are impossible to resolve. I had to use the
--legacy-peer-depsoption to successfully install.I would have a go myself, but I'm unsure of whether there are any conscious decisions to have the current set up.