Continuing Issue - In a class and attempting to follow instructor

[djmill2]

I keep getting an issue with not having phantomJS loaded:

Then I attempted to load the karma-phantomjs-launcer - using the instruction from on the NPM site and as you can see below it failed as well. I will upload this log as well.

See Below:
PS C:\Users\Louise\Documents\mytodo> npm test

@ test C:\Users\Louise\Documents\mytodo
gulp test

[09:59:36] Loading C:\Users\Louise\Documents\mytodo\gulp_tasks\browsersync.js
[09:59:37] Loading C:\Users\Louise\Documents\mytodo\gulp_tasks\karma.js
[09:59:38] Loading C:\Users\Louise\Documents\mytodo\gulp_tasks\misc.js
[09:59:38] Loading C:\Users\Louise\Documents\mytodo\gulp_tasks\webpack.js
[09:59:38] Using gulpfile ~\Documents\mytodo\gulpfile.js
[09:59:38] Starting 'test'...
[09:59:38] Starting 'karma:single-run'...
22 06 2018 09:59:39.178:ERROR [config]: Error in config file!
{ Error: Cannot find module 'karma-phantomjs-launcher'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:594:15)
at Function.Module._load (internal/modules/cjs/loader.js:520:25)
at Module.require (internal/modules/cjs/loader.js:650:17)
at require (internal/modules/cjs/helpers.js:20:18)
at module.exports (C:\Users\Louise\Documents\mytodo\conf\karma.conf.js:40:7)
at Object.parseConfig (C:\Users\Louise\Documents\mytodo\node_modules\karma\lib\config.js:410:5)
at new Server (C:\Users\Louise\Documents\mytodo\node_modules\karma\lib\server.js:56:20)
at karmaSingleRun (C:\Users\Louise\Documents\mytodo\gulp_tasks\karma.js:19:23)
at taskWrapper (C:\Users\Louise\Documents\mytodo\node_modules\undertaker\lib\set-task.js:13:15)
at taskWrapper (C:\Users\Louise\Documents\mytodo\node_modules\undertaker\lib\set-task.js:13:15)
at taskWrapper (C:\Users\Louise\Documents\mytodo\node_modules\undertaker\lib\set-task.js:13:15)
at bound (domain.js:396:14)
at runBound (domain.js:409:12)
at asyncRunner (C:\Users\Louise\Documents\mytodo\node_modules\async-done\index.js:55:18)
at process._tickCallback (internal/process/next_tick.js:61:11)
at Function.Module.runMain (internal/modules/cjs/loader.js:746:11) code: 'MODULE_NOT_FOUND' }
[09:59:39] The following tasks did not complete: test, karma:single-run
[09:59:39] Did you forget to signal async completion?
npm ERR! Test failed. See above for more details.

INSTALL Failed:

PS C:\Users\Louise\Documents\mytodo> npm install --save-dev karma-phantomjs-launcher

phantomjs-prebuilt@2.1.16 install C:\Users\Louise\Documents\mytodo\node_modules\phantomjs-prebuilt
node install.js

PhantomJS not found on PATH
Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-windows.zip
Saving to C:\Users\Louise\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip
Receiving...

Error making request.
Error: self signed certificate in certificate chain
at TLSSocket.onConnectSecure (_tls_wrap.js:1048:34)
at TLSSocket.emit (events.js:182:13)
at TLSSocket._finishInit (_tls_wrap.js:628:8)

Please report this full log at https://github.com/Medium/phantomjs
npm WARN webpack-fail-plugin@1.0.6 requires a peer of webpack@^1.9.11 but none is installed. You must install peer dependencies yourself.
npm WARN mytodo No description
npm WARN mytodo No repository field.
npm WARN mytodo No license field.
npm WARN The package es6-shim is included as both a dev and production dependency.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! phantomjs-prebuilt@2.1.16 install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the phantomjs-prebuilt@2.1.16 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! C:\Users\Louise\AppData\Roaming\npm-cache_logs\2018-06-22T16_07_18_629Z-debug.log
PS C:\Users\Louise\Documents\mytodo>

LOG
2018-06-22T16_07_18_629Z-debug.log