Cannot `npm start` @ windows

Running npm start (as suggested in the “Local Previews” section) throws errors at me. I am quite sure this is a windows-specific error since Der Befehl "." ist entweder falsch geschrieben oder konnte nicht gefunden werden. translates roughly to Command "." not found

Yes, I did run npm install && cd website && npm install && cd .. and it worked fine. And yes, I am sorry, but I have to use windows.

λ npm start
> uppy@0.24.4 start C:\Users\cornelius\src\uppy
> npm-run-all --parallel watch start:server web:preview
> uppy@0.24.4 watch C:\Users\cornelius\src\uppy
> npm-run-all --parallel watch:js watch:css
> uppy@0.24.4 start:server C:\Users\cornelius\src\uppy
> node bin/start-server
> uppy@0.24.4 web:preview C:\Users\cornelius\src\uppy
> npm-run-all --parallel web:examples:watch web:bundle:update:watch web:serve
> uppy@0.24.4 watch:css C:\Users\cornelius\src\uppy
> onchange 'src/scss/**/*.scss' --initial --verbose -- npm run build:css
> uppy@0.24.4 web:examples:watch C:\Users\cornelius\src\uppy
> cd website && node build-examples.js watch
> uppy@0.24.4 web:bundle:update:watch C:\Users\cornelius\src\uppy
> onchange 'dist/**/*.css' 'dist/**/*.js' --initial --verbose -- node website/update.js
> uppy@0.24.4 web:serve C:\Users\cornelius\src\uppy
> cd website && ./node_modules/.bin/hexo server
> uppy@0.24.4 watch:js C:\Users\cornelius\src\uppy
> onchange 'src/**/*.js' --initial --verbose -- npm run build:bundle
Der Befehl "." ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! uppy@0.24.4 web:serve: `cd website && ./node_modules/.bin/hexo server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the uppy@0.24.4 web:serve 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:\Users\cornelius\AppData\Roaming\npm-cache\_logs\2018-05-18T21_51_47_719Z-debug.log
ERROR: "web:serve" exited with 1.
onchange: watching 'src/scss/**/*.scss'
onchange: executing command "npm run build:css"
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! uppy@0.24.4 web:preview: `npm-run-all --parallel web:examples:watch web:bundle:update:watch web:serve`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the uppy@0.24.4 web:preview 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!?[35m?[0m     C:\Users\cornelius\AppData\Roaming\npm-cache\_logs\2018-05-18T21_51_48_413Z-debug.log
onchange: watching 'src/**/*.js'
onchange: executing command "npm run build:bundle"
ERROR: "web:preview" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! uppy@0.24.4 start: `npm-run-all --parallel watch start:server web:preview`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the uppy@0.24.4 start 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:\Users\cornelius\AppData\Roaming\npm-cache\_logs\2018-05-18T21_51_48_877Z-debug.log

Here is the node error log:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\cornelius\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'web:preview' ]
2 info using npm@6.0.1
3 info using node@v8.11.1
4 verbose run-script [ 'preweb:preview', 'web:preview', 'postweb:preview' ]
5 info lifecycle uppy@0.24.4~preweb:preview: uppy@0.24.4
6 info lifecycle uppy@0.24.4~web:preview: uppy@0.24.4
7 verbose lifecycle uppy@0.24.4~web:preview: unsafe-perm in lifecycle true
8 verbose lifecycle uppy@0.24.4~web:preview: PATH: C:\Users\cornelius\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\cornelius\src\uppy\node_modules\.bin;C:\Users\cornelius\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\cornelius\src\uppy\node_modules\.bin;C:\Users\cornelius\bin\cmder\bin;C:\Users\cornelius\bin\cmder\vendor\git-for-windows\bin;C:\Users\cornelius\bin\cmder\vendor\git-for-windows\usr\bin;C:\Users\cornelius\bin\cmder\vendor\git-for-windows\share\vim\vim74;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Users\cornelius\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files\Git\cmd;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Go\bin;C:\Program Files\nodejs\;C:\Program Files (x86)\Elm Platform\0.17\bin;C:\Users\cornelius\AppData\Local\Programs\Python\Python35-32\Scripts\;C:\Users\cornelius\AppData\Local\Programs\Python\Python35-32\;C:\Users\cornelius\bin\apache-maven-3.3.9\bin;C:\Program Files\Java\jdk1.8.0_92\bin;C:\Users\cornelius\bin\activator-1.3.10-minimal\bin;C:\Users\cornelius\bin\pt;C:\Users\cornelius\bin\emacs\bin;C:\Users\cornelius\AppData\Local\Microsoft\WindowsApps;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Program Files (x86)\Sophos\Sophos SSL VPN Client\bin;C:\Users\cornelius\AppData\Roaming\npm;C:\Users\cornelius\AppData\Local\Google\Cloud SDK\google-cloud-sdk\bin;C:\Users\cornelius\bin\cmder
9 verbose lifecycle uppy@0.24.4~web:preview: CWD: C:\Users\cornelius\src\uppy
10 silly lifecycle uppy@0.24.4~web:preview: Args: [ '/d /s /c',
10 silly lifecycle   'npm-run-all --parallel web:examples:watch web:bundle:update:watch web:serve' ]
11 silly lifecycle uppy@0.24.4~web:preview: Returned: code: 1  signal: null
12 info lifecycle uppy@0.24.4~web:preview: Failed to exec web:preview script
13 verbose stack Error: uppy@0.24.4 web:preview: `npm-run-all --parallel web:examples:watch web:bundle:update:watch web:serve`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\cornelius\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:283:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\cornelius\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid uppy@0.24.4
15 verbose cwd C:\Users\cornelius\src\uppy
16 verbose Windows_NT 10.0.16299
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\cornelius\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "web:preview"
18 verbose node v8.11.1
19 verbose npm  v6.0.1
20 error code ELIFECYCLE
21 error errno 1
22 error uppy@0.24.4 web:preview: `npm-run-all --parallel web:examples:watch web:bundle:update:watch web:serve`
22 error Exit status 1
23 error Failed at the uppy@0.24.4 web:preview script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

[sne11ius]

I did try bash, but it didn’t work too well. Bash didn’t want to run my windows installation of npm/node. After I apt-get-installed node to ubunto I got other nasty messages and gave up.

You can close this issue if you want - I will not try any workarounds since I want to keep my sanity 😉

Just in case you’re wondering why I was doing this: I need a firebase-storage backend for uppy. I implemented a small plugin and it seems to do what I want so far - feel free to copy the code or whatever:

https://github.com/sne11ius/egghead.space/blob/feature/file_upload/src/service/FirebaseCloudStorage.js

[pauln]

Just in case anyone else comes across this thread while trying to run npm start on Windows: yes, it does appear to work on bash on Windows. You’ll need to get Node and npm up and running within it first, if you haven’t used them before - otherwise it’ll attempt to use the versions you have installed in your Windows host system, which won’t work at all.