[v6] kitchen sink unable to install

Hello:
Due to have examples on migrating app from v5 to v6 i’ve try to install Kitchen Sink…

I’ve follow:

I’ve download

The installation npm install send me lots of vulnerabilities
And when i exec: npm run core it send me errors too…

C:\framework7-master>npm install

> [email protected] postinstall C:\framework7-master
> echo "Love Framework7? Support project by donating or pledging on patreon:
 > https://patreon.com/vladimirkharlampidi
"

"Love Framework7? Support project by donating or pledging on patreon:
npm WARN @rollup/[email protected] requires a peer of [email protected]^1.20.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\rollup\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

audited 1658 packages in 6.094s

68 packages are looking for funding
  run `npm fund` for details

found 21 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details

found 21 low severity vulnerabilities in 1658 scanned packages
run npm audit fix to fix 8 of them.
4 vulnerabilities require semver-major dependency updates.
9 vulnerabilities require manual review. See the full report for details.

C:\framework7-master>npm run core

> [email protected] core C:\framework7-master
> cross-env-shell NODE_ENV=development CORE_BUILD_ONLY_UMD=true "gulp build-core && gulp ks-core && gulp server-core"

[12:36:49] Using gulpfile C:\framework7-master\gulpfile.js
[12:36:49] Starting 'build-core'...
[12:36:49] Starting 'core-clean'...
"xargs" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
[12:36:49] 'core-clean' errored after 37 ms
[12:36:49] Error: Shell command exit with non zero code: 255
    at ChildProcess.<anonymous> (C:\framework7-master\node_modules\exec-sh\lib\exec-sh.js:73:15)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:529:15)
    at maybeClose (internal/child_process.js:1048:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
    at Process.callbackTrampoline (internal/async_hooks.js:131:14)
[12:36:49] 'build-core' errored after 43 ms
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: spawn gulp build-core && gulp ks-core && gulp server-core ENOENT
    at notFoundError (C:\framework7-master\node_modules\cross-spawn\lib\enoent.js:6:26)
    at verifyENOENT (C:\framework7-master\node_modules\cross-spawn\lib\enoent.js:40:16)
    at ChildProcess.cp.emit (C:\framework7-master\node_modules\cross-spawn\lib\enoent.js:27:25)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess.cp.emit (C:\framework7-master\node_modules\cross-spawn\lib\enoent.js:30:37)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12) {
  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'spawn gulp build-core && gulp ks-core && gulp server-core',
  path: 'gulp build-core && gulp ks-core && gulp server-core',
  spawnargs: []
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] core: `cross-env-shell NODE_ENV=development CORE_BUILD_ONLY_UMD=true "gulp build-core && gulp ks-core && gulp server-core"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] core 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!     C:\...........\AppData\Roaming\npm-cache\_logs\2021-02-09T11_36_49_976Z-debug.log
1 Like

I am facing the same issue. Have to managed to resolve it?

Hello,
I haven’t resolve it yet… sorry.As soon as i resolve it i will post here the solution…

1 Like

Seems like the build scripts don’t support Windows, see also Windows installation - #4 by eikowagenknecht