Develop Reference

"spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell ENOENT" error while running npm start

When ever I try to execute npm start, this is what happens. I think there is some issue with powershell and not with npm because npm starts the development server. BTW I created basic react app using npx create-react-app. I checked, powershell file is there in the specified location and it is working as well. Guild me what should I do in order to resolve the error.
events.js:353
throw er; // Unhandled 'error' event
^
Error: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:467:16)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
at onErrorNT (internal/child_process.js:467:16)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell',
path: 'C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell',
spawnargs: [
'-NoProfile',
'-NonInteractive',
'–ExecutionPolicy',
'Bypass',
'-EncodedCommand',
'UwB0AGEAcgB0ACAAIgBoAHQAdABwADoALwAvAGwAbwBjAGEAbABoAG8AcwB0ADoAMwAwADAAMAAiAA=='
]
}

I faced with a same problem on Windows 10.
And solution was a pretty simple - just run your commands in git bush console.

Step 1:(reason of the error)
go to C:\Windows\System32\WindowsPowerShell\v1.0 and then you will not be found powershell.exe file that folder.
Step 2: (solution of the error)
download powershell.exe file online or just copy and paste this file in C:\Windows\System32\WindowsPowerShell\v1.0
https://www.exefiles.com/en/exe/powershell-exe/ - To download powershell.exe file online

So after trying everything and looking for the error on every possible website. I still wasn't able to resolve the error. Then I personally talked to someone regarding the error and he suggested me to run it in Windows Sub-system for Linux (WSL). I exactly did that and installed WSL with Linux 20.04 LTS. Now I am using Unix terminal to create the react app. It isn't the best solution for the problem, but yeah it does work and saves a lot of time!

when i am trying to run mupx deploy it is showing error

error in console
shubhabrata#shubhabrata-VirtualBox:~/Meteor/myapp$ mupx deploy
Meteor Up: Production Quality Meteor Deployments
Configuration file : mup.json
Settings file : settings.json
“ Checkout Kadira!
It's the best way to monitor performance of your app.
Visit: https://kadira.io/mup ”
Meteor app path : /home/shubhabrata/Meteor/myapp
Using buildOptions : {}
buffer.js:80
throw new Error(
^
Error: If encoding is specified then the first argument must be a string
at new Buffer (buffer.js:80:13)
at Readable. (/usr/lib/node_modules/mupx/node_modules/archiver/lib/util/index.js:32:15)
at emitNone (events.js:91:20)
at Readable.emit (events.js:188:7)
at endReadableNT (_stream_readable.js:975:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)

Switching from node 7 to node 5.12 worked for me. I installed using nvm so that I can use later node versions in the future.
This occurred for me while using (deliberately) an old version of mup. It could well be that just upgrading mup will fix the problem.

One of the two Meteor examples does not work on Windows 10

Installed Meteor v1.4.1.2, completed the basic Simple Todos tutorial and wanted to check the two examples mentioned in it:
meteor create --example localmarket
meteor create --example todos
And Run Todos sample will get error!
\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:165
throw error;
^
Error: unexpected eof
at decorate (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\abstract.js:67:36)
at Extract.Abstract.error (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\abstract.js:61:12)
at Extract._streamEnd (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\tar\lib\extract.js:91:35)
at BlockStream.<anonymous> (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\tar\lib\parse.js:51:8)
at emitNone (events.js:67:13)
at BlockStream.emit (events.js:166:7)
at BlockStream._emitChunk (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\block-stream\block-stream.js:203:10)
at BlockStream.resume (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\block-stream\block-stream.js:58:15)
at Extract.Reader.resume (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\reader.js:242:34)
at Entry.<anonymous> (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\tar\lib\parse.js:261:8)
at emitNone (events.js:67:13)
at Entry.emit (events.js:166:7)
at Entry.resume (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\tar\lib\entry.js:93:8)
at resume (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\collect.js:62:16)
at unblockEntry (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\collect.js:43:28)
at Entry.<anonymous> (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\collect.js:47:9)
at FileWriter.<anonymous> (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\dir-writer.js:146:11)
at emitNone (events.js:67:13)
at FileWriter.emit (events.js:166:7)
at WriteStream.<anonymous> (C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\fstream\lib\file-writer.js:45:10)
at emitOne (events.js:77:13)
at WriteStream.emit (events.js:169:7)
at C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\graceful-fs\graceful-fs.js:214:14
at C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\graceful-fs\graceful-fs.js:241:16
at C:\Users\aboo\AppData\Local\.meteor\packages\meteor-tool\1.4.1_2\mt-os.windows.x86_32\dev_bundle\lib\node_modules\cordova-lib\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:232:16
at FSReqWrap.oncomplete (fs.js:82:15)

Meteor 1.4.1.1 has a bug with Windows 10. You can find a solution for your problem in this issue - https://github.com/meteor/meteor/issues/7703 # Meteor's GitHub.

The above meteor basics examples
meteor create --example localmarket
meteor create --example todos
are created using meteor older versions . current using meteor version is 1.4
the above examples are created 1.3 .SO need to update the programmes are packages.

Loopback lb-services.js Docular Error: Error: EPERM: operation not permitted,

I´m trying to generate the docs for the lb-services.js file of the Loopback Angular SDK. Howerver I´m getting this weird error when running grunt.
Running "docular" task
(node:18260) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:18260) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Loading individual files for gid: Base
Loading individual files for gid: loopback
Loading individual files for gid: lbServices
Parsing files for gid: Base
Parsing files for gid: loopback
Parsing files for gid: lbServices
Backfilling file data for gid: Base
Backfilling file data for gid: loopback
Backfilling file data for gid: lbServices
Creating docs from for gid: Base
Creating docs from for gid: loopback
Creating docs from for gid: lbServices
Error: EPERM: operation not permitted, open 'docular_generated\sources\lb-services.js'
at Error (native)
at Object.fs.openSync (fs.js:634:18)
at copyFileSync (node_modules\fs-extra\lib\copy-sync\copy-file-sync.js:21:16)
at Object.copySync (node_modules\fs-extra\lib\copy-sync\copy-sync.js:32:7)
at .<anonymous> (node_modules\docular\lib\scripts\core\generator.js:132:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (C:\Users\pablo\Dropbox\Nozzmo\Reuniones\exeboard\backend\node_modules\async-listener\index.js:450:15)
From previous event:
at Group.extend.exportDocFiles (node_modules\docular\lib\scripts\core\generator.js:123:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (node_modules\async-listener\index.js:450:15)
{ Error: EPERM: operation not permitted, open 'docular_generated\sources\lb-services.js'
at Error (native)
at Object.fs.openSync (fs.js:634:18)
at copyFileSync (node_modules\fs-extra\lib\copy-sync\copy-file-sync.js:21:16)
at Object.copySync (node_modules\fs-extra\lib\copy-sync\copy-sync.js:32:7)
at .<anonymous> (node_modules\docular\lib\scripts\core\generator.js:132:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (node_modules\async-listener\index.js:450:15)
From previous event:
at Group.extend.exportDocFiles (node_modules\docular\lib\scripts\core\generator.js:123:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (node_modules\async-listener\index.js:450:15)
errno: -4048,
code: 'EPERM',
syscall: 'open',
path: 'docular_generated\\sources\\lb-services.js' }
Warning: Task "docular" failed. Use --force to continue.
Aborted due to warnings.
I´m using Windows 10 and Node v6.0.0. The gruntfile just contains the
'loopback_sdk_angular', 'docular',
'uglify'
taks.
Can anyone help me find the cause of this error?

Error starting a test with testacular

I am trying out the angularjs tutorials on a 64 bit Windows 7 system because I find this framework quite interesting from what I read on its home page. I am a newbie to node.js and not experienced in Java-Script.
When running the tests, I get the following error. Can anybody find out what the problem is or give some hints how to determine that? I have a fresh Installation of node and added testacular with
npm install -g testacular
which worked fine from what was printed on the console window.
So here is the error message:
PS C:\Users\xx\Documents\Angular\angular-phonecat> .\scripts\test.bat
INFO [testacular]: Testacular server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
ERROR [testacular]: { [Error: spawn ENOENT] code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn' }
Error: spawn ENOENT
at errnoException (child_process.js:948:11)
at Process.ChildProcess._handle.onexit (child_process.js:739:34)

Short answer:
Set env variable CHROME_BIN to full path to chrome.exe
The error msg is confusing, as the behavior of spawn got changed in Node 0.10, we need to update it (https://github.com/karma-runner/karma/issues/452)

Inserting 'PhantomJS' for the test browser in the karma configuration file on Windows Vista resulted in the same error message: { [Error: spawn ENOENT] code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn' }
I ad-libbed on the advice above and inserted in the system path ("Environmental Variables") under "User variables for owner" PHANTOMJS_BIN with the value consisting of the path including phantomjs.exe (C:\Program Files\phantomjs-1.9.0-windows\phantomjs.exe)
All good, jasmine angularjs tests running now and much faster than with 'Chrome' or 'Firefox' as the test browser.