search

linkedpipes / dcat-ap-forms

Forms application for filling out DCAT-AP v2.0.0 compatible metadata
MIT License
2 stars 2 forks source link

Cannot npm install #98

Closed jakubklimek closed 4 years ago

jakubklimek commented 4 years ago 
klimek@xrg11:/opt/dcat-ap-forms-vue$ sudo npm i

> fibers@4.0.2 install /opt/dcat-ap-forms-vue/node_modules/fibers
> node build.js || nodejs build.js

internal/modules/cjs/loader.js:796
    throw err;
    ^

Error: Cannot find module '/opt/dcat-ap-forms-vue/node_modules/fibers/build.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:17)
    at Function.Module._load (internal/modules/cjs/loader.js:686:27)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
    at internal/main/run_main_module.js:17:11 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
internal/modules/cjs/loader.js:796
    throw err;
    ^

Error: Cannot find module '/opt/dcat-ap-forms-vue/node_modules/fibers/build.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:17)
    at Function.Module._load (internal/modules/cjs/loader.js:686:27)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
    at internal/main/run_main_module.js:17:11 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/watchpack/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fibers@4.0.2 install: `node build.js || nodejs build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fibers@4.0.2 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-02-13T12_14_42_071Z-debug.log
jakubklimek commented 4 years ago

caused by some weird permissions problem while building fibers.