Topic on Talk:Parsoid

Orthogonal to Parsoid

Cmd error:

C:\windows\system32>npm install parsoid

> contextify@0.1.15 install C:\windows\system32\node_modules\contextify

> node-gyp rebuild

C:\windows\system32\node_modules\contextify>if not defined npm_config_node_gyp (

node "C:\Users\Lau\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\

node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild )

gyp: binding.gyp not found (cwd: C:\windows\system32\node_modules\contextify) wh

ile trying to load binding.gyp

gyp ERR! configure error

gyp ERR! stack Error: `gyp` failed with exit code: 1

gyp ERR! stack     at ChildProcess.onCpExit (C:\Users\Lau\AppData\Roaming\npm\no

de_modules\npm\node_modules\node-gyp\lib\configure.js:305:16)

gyp ERR! stack     at emitTwo (events.js:106:13)

gyp ERR! stack     at ChildProcess.emit (events.js:191:7)

gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces

s.js:215:12)

gyp ERR! System Windows_NT 6.1.7601

gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Lau\\AppData\

\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "reb

uild"

gyp ERR! cwd C:\windows\system32\node_modules\contextify

gyp ERR! node -v v6.7.0

gyp ERR! node-gyp -v v3.4.0

gyp ERR! not ok

C:\windows\system32

`-- parsoid@0.5.2

`-- pegjs@0.8.0  (git+https://github.com/tstarling/pegjs.git#9162b1e114e41992d

d0fdafa24d2574a0b8a836a)

npm WARN enoent ENOENT: no such file or directory, open 'C:\windows\system32\pac

kage.json'

npm WARN system32 No description

npm WARN system32 No repository field.

npm WARN system32 No README data

npm WARN system32 No license field.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: contextify@0.1.15 (node_modules\

contextify):

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: contextify@0.1.15 install: `node

-gyp rebuild`

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

Can you try doing this somewhere other than C:\windows\system32?

Like C:\Users\[USERNAME]

I still have error there

Can you try with npm install parsoid --no-optional?

We've removed the html5 library as a dependency, so contextify should no longer be an issue, even without --no-optional.

OMG. I think i seleted worng option installing git and i also didn't set up the username and email. LoL

And also reinstalling node.js

Also i switch to git cmd but i got this error: npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) npm WARN addRemoteGit git+https://github.com/wikimedia/content-type.git#47b2632d0a2ee79a7d67268e2f6621becd95d05b resetting remote C:\Users\Lau\AppData\Roaming\npm-cache\_git-remotes\git-https-github-com-wikimedia-content-type-git-47b2632d0a2ee79a7d67268e2f6621becd95d05b-0dff22de because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) npm WARN addRemoteGit killed: false, npm WARN addRemoteGit code: 1, npm WARN addRemoteGit signal: null, npm WARN addRemoteGit cmd: 'git -c core.longpaths=true config --get remote.origin.url' } npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) npm WARN addRemoteGit git+https://github.com/arlolra/negotiator.git#0418ab4e9a665772b7e233564a4525c9d9a8ec3a resetting remote C:\Users\Lau\AppData\Roaming\npm-cache\_git-remotes\git-https-github-com-arlolra-negotiator-git-0418ab4e9a665772b7e233564a4525c9d9a8ec3a-164c7910 because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) npm WARN addRemoteGit killed: false, npm WARN addRemoteGit code: 1, npm WARN addRemoteGit signal: null, npm WARN addRemoteGit cmd: 'git -c core.longpaths=true config --get remote.origin.url' } npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Socket.<anonymous> (internal/child_process.js:334:11) npm WARN addRemoteGit at emitOne (events.js:96:13) npm WARN addRemoteGit at Socket.emit (events.js:188:7) npm WARN addRemoteGit at Pipe._handle.close [as _onclose] (net.js:501:12) npm WARN addRemoteGit git+https://github.com/tstarling/pegjs.git#9162b1e114e41992dd0fdafa24d2574a0b8a836a resetting remote C:\Users\Lau\AppData\Roaming\npm-cache\_git-remotes\git-https-github-com-tstarling-pegjs-git-9162b1e114e41992dd0fdafa24d2574a0b8a836a-96a2073a because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Socket.<anonymous> (internal/child_process.js:334:11) npm WARN addRemoteGit at emitOne (events.js:96:13) npm WARN addRemoteGit at Socket.emit (events.js:188:7) npm WARN addRemoteGit at Pipe._handle.close [as _onclose] (net.js:501:12) npm WARN addRemoteGit killed: false, npm WARN addRemoteGit code: 1, npm WARN addRemoteGit signal: null, npm WARN addRemoteGit cmd: 'git -c core.longpaths=true config --get remote.origin.url' } npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) npm WARN addRemoteGit git+https://github.com/gwicke/kad.git#f35971036f43814043245da82b12d035b7bbfd16 resetting remote C:\Users\Lau\AppData\Roaming\npm-cache\_git-remotes\git-https-github-com-gwicke-kad-git-f35971036f43814043245da82b12d035b7bbfd16-48a8d777 because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url npm WARN addRemoteGit npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12) npm WARN addRemoteGit at emitTwo (events.js:106:13) npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7) npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16) npm WARN addRemoteGit at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) npm WARN addRemoteGit killed: false, npm WARN addRemoteGit code: 1, npm WARN addRemoteGit signal: null, npm WARN addRemoteGit cmd: 'git -c core.longpaths=true config --get remote.origin.url' }

Are you behind a corporate firewall blocking connections to https://github.com?

no.

Ok, well, that issue seems unrelated to installing Parsoid in particular.

You should first confirm that your system is setup to git clone repositories and that you can npm install git urls.

how can i do that?

Well, first try,

git clone https://github.com/tstarling/pegjs

then try,

npm install git+https://github.com/tstarling/pegjs