Error installing ParaViewWeb with npm install paraviewweb --save about paraviewweb

[jourdain]

Unfortunately yes... ;-(

We haven't tried to build/develop ParaViewWeb on a Windows system hence the unknown behavior you are noticing.

I guess, if we assume node 4+ and npm 3+, I should be able to remove the post install script which obviously fails on Windows.
But on your system, it seems that "ws" also bring its set of issues...

Anyway, thanks for reporting back...

[rpelorosso]

I see, thanks for answering! I don't have a Mac, but I guess it should work fine in Linux, right?

[jourdain]

Yes it should. Thanks for your patience.

[rpelorosso]

Excellent! I'll try it in Linux then :) Thanks YOU for your hard work! :)

[mathturtle]

I work mostly on a paraviewweb based application, but my main development platform is Linux. So it should work fine on Linux. You'll probably have to install your own node/npm, the one in my package manager (Ubuntu 15.10) was too old.

[rpelorosso]

Thanks @mathturtle ! I'm trying to install it using Arch Linux. My nodejs version is 6.1.0 and my npm version is 3.8.9.

When running npm install paraviewweb, the following happens (pasted below). Looks like fix-kw-web-suite is missing. Do you know why this might be happening? Thanks!

silencer@myhostname ~]$ npm install paraviewweb
npm WARN deprecated [email protected]: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.

[email protected] install /home/silencer/node_modules/bufferutil
node-gyp rebuild

make: Entering directory '/home/silencer/node_modules/bufferutil/build'
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/obj.target/bufferutil.node
COPY Release/bufferutil.node
make: Leaving directory '/home/silencer/node_modules/bufferutil/build'

[email protected] install /home/silencer/node_modules/utf-8-validate
node-gyp rebuild

make: Entering directory '/home/silencer/node_modules/utf-8-validate/build'
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/obj.target/validation.node
COPY Release/validation.node
make: Leaving directory '/home/silencer/node_modules/utf-8-validate/build'

[email protected] postinstall /home/silencer/node_modules/paraviewweb
fix-kw-web-suite || true

sh: fix-kw-web-suite: command not found
/home/silencer
└─┬ [email protected]
├─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ ├─┬ [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └─┬ [email protected]
│ │ │ ├── [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├─┬ [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ └── [email protected]
│ └── [email protected]
├── [email protected]
├── [email protected]
└─┬ [email protected]
├─┬ [email protected]
│ ├── [email protected]
│ └── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

npm WARN enoent ENOENT: no such file or directory, open '/home/silencer/package.json'
npm WARN silencer No description
npm WARN silencer No repository field.
npm WARN silencer No README data
npm WARN silencer No license field.
[silencer@myhostname ~]$

[jourdain]

That's expected and you don't need to worry about it. That's why the command it run is:

"fix-kw-web-suite || true"

[rpelorosso]

Thanks @jourdain ! What about the

npm WARN enoent ENOENT: no such file or directory, open '/home/silencer/package.json'
npm WARN silencer No description
npm WARN silencer No repository field.
npm WARN silencer No README data
npm WARN silencer No license field.

messages, is that normal?

[jourdain]

Are you installing it for one of your web project?
ParaViewWeb is just a Web library and does not provide any executable.
So when you ask npm to install it, npm assume it is to add it into you
local web project.
If npm can't find your package.json, then it print that it couldn't find
your web project.

On Thu, May 12, 2016 at 12:45 PM, rpelorosso [email protected]
wrote:

Thanks @jourdain https://github.com/jourdain ! What about the

npm WARN enoent ENOENT: no such file or directory, open
'/home/silencer/package.json'
npm WARN silencer No description
npm WARN silencer No repository field.
npm WARN silencer No README data
npm WARN silencer No license field.

messages, is that normal?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#107 (comment)

[rpelorosso]

Thank you @jourdain, that makes A LOT of sense. I just have one more question, where can I find the code for this http://www.paraview.org/wp-content/uploads/2014/07/Viz-1024x695.png example?. I know that ParaView 4.1.0 comes with \paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py which seems to be an older version of the Visualizer presented in the linked screenshot, but ParaView 5.0 doesn't seem to come with any python server code nor client examples.

[jourdain]

ParaView 5.0 should have the exact same JS code as paraview 4.4.

I don't even know why ParaView 5.0 won't have the Web code (unless you are
on windows).

On Thu, May 12, 2016 at 1:33 PM, rpelorosso [email protected]
wrote:

Thank you @jourdain https://github.com/jourdain, that makes A LOT of
sense. I just have one more question, where can I found the code for this
http://www.paraview.org/wp-content/uploads/2014/07/Viz-1024x695.png
example?. I know that ParaView 4.1.0 comes with
\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py which seems
to be an older version of the Visualizer presented in the linked
screenshot, but ParaView 5.0 doesn't seem to come with any python server
code examples.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#107 (comment)

[rpelorosso]

Yes, you're right and I feel like a fool :P It is there, thank you very much!