Skip to content
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

Closed
hayley-leblanc opened this issue Jul 31, 2019 · 7 comments
Closed

Can't build Visualizer in development #81

hayley-leblanc opened this issue Jul 31, 2019 · 7 comments
Labels

Comments

@hayley-leblanc
Copy link

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 run npm run build, I get some errors about missing babel presets/plugins. I was able to resolve some of them on my own by just installing them using npm, but now I'm getting the error Plugin/Preset files are not allowed to export objects, only functions. when I try to run npm run build. Is this issue probably on my end, or is it an issue with the Visualizer? Thanks so much!

@jourdain
Copy link
Collaborator

Did you run npm install?
Are you on Windows?

@hayley-leblanc
Copy link
Author

I did run npm install and I am on Linux Mint.

@hayley-leblanc
Copy link
Author

I also tried on a Mac and ran into the same error.

@jourdain
Copy link
Collaborator

jourdain commented Aug 1, 2019

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.
You might be able to checkout older version to start working on removing the remote rendering part. Sorry for the inconvenience.

@jourdain
Copy link
Collaborator

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

@hayley-leblanc
Copy link
Author

Thank you!

@jourdain
Copy link
Collaborator

🎉 This issue has been resolved in version 3.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants