Hello and thanks for the prompt reply! I looked more into the problem, and it seems that the issue was with the included webpack.config.js configuration file. I am not sure what caused the original error, but I was also getting this error:
[webpack-cli] Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
- configuration.devtool should match pattern "^(inline-|hidden-|eval-)?(nosources-)?(cheap-(module-)?)?source-map$".
BREAKING CHANGE since webpack 5: The devtool option is more strict.
Please strictly follow the order of the keywords in the pattern.
Within the included webpack.config.js file, there’s the line:
devtool: 'cheap-eval-source-map'
which was out of order. I changed it to:
devtool: 'eval-cheap-source-map'
which allowed me to build everything with the latest npm version and following all the semantic versioning in the package.json file. After messing with nvm earlier, and changing specific versions of dependencies, I was unable to reproduce the openSSL error, but swapping the order in the devtool: instructions allowed for a successful build.
Now, I am able to run the panel as intended (as far as I can tell). One panel has a “Hello, there” play button, and the other panel has some RGB sliders. I did not use npm audit fix or any of the variants, opting to just leave things as is.