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
Can't build Visualizer in development #81
Comments
Did you run |
I did run |
I also tried on a Mac and ran into the same error. |
I've just tried it on my mac and I can indeed reproduce the issue. I'll see what I can do to solve it. |
It seems that the issue is out of our end. I hope npm will solve the issue on their server. https://npm.community/t/dependencies-reported-by-npm-does-not-match-package-json/9478 |
Thank you! |
🎉 This issue has been resolved in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hello! I am working with ParaView Visualizer and I want to disable remote rendering. My current instance of ParaViewWeb and the Visualizer were downloaded from https://www.paraview.org/download/, so I didn't have to build them, but since I need to change the ParaView source code, I've been trying to set it up as described here https://github.com/Kitware/visualizer#development. However, I'm running into
npm
issues when I do so - when I runnpm run build
, I get some errors about missingbabel
presets/plugins. I was able to resolve some of them on my own by just installing them usingnpm
, but now I'm getting the errorPlugin/Preset files are not allowed to export objects, only functions.
when I try to runnpm run build
. Is this issue probably on my end, or is it an issue with the Visualizer? Thanks so much!The text was updated successfully, but these errors were encountered: