Getting Error protractor_1.browser.action is not a function - protractor

I am facing an error while performing actions.
Code of Specs file
it("testcase action", async()=> {
browser.waitForAngularEnabled(false);
await browser.get("https://google.com");
await browser.actions().mouseMove(element(by.css("input[name='q']"))).sendKeys("protrac").perform();
await browser.sleep(8000);
await browser.actions().sendKeys(protractor.Key.ARROW_DOWN);
await browser.action().sendKeys(protractor.Key.ENTER);
})
Code from Config File
import {Config, browser} from "protractor";
// An example configuration file
export let config: Config = {
// The address of a running selenium server.
//seleniumAddress: 'http://localhost:4444/wd/hub',
directConnect:true,
// Capabilities to be passed to the webdriver instance.
capabilities: {
browserName: 'chrome',
'goog: chromeOptions':{
w3c: false
},
},
// Spec patterns are relative to the configuration file location passed
// to protractor (in this example conf.js).
// They may include glob patterns.
specs: ['testspec.js'],
// Options to be passed to Jasmine-node.
jasmineNodeOpts: {
showColors: true, // Use colors in the command line report.
}
};
Error i am facing
> protractortypescriptcucumberframework#1.0.0 pretest C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework
> tsc
> protractortypescriptcucumberframework#1.0.0 test C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework
> protractor JSFiles/configuration.js
[12:35:49] I/launcher - Running 1 instances of WebDriver
[12:35:50] I/direct - Using ChromeDriver directly...
DevTools listening on ws://127.0.0.1:50594/devtools/browser/c5170ccf-5c5d-408d-8d10-c6eb3022c11f
Started
(node:7448) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues.
Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
F
Failures:
1) Action class testcase action
Message:
Failed: protractor_1.browser.action is not a function
Stack:
TypeError: protractor_1.browser.action is not a function
at C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework\testspec.ts:110:15
at Generator.next (<anonymous>)
at fulfilled (C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework\JSFiles\testspec.js:5:58)
From: Task: Run it("testcase action") in control flow
at UserContext.<anonymous> (C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework\node_modules\jasminewd2\index.js:94:19)
From asynchronous test:
Error
at C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework\testspec.ts:102:1
at Generator.next (<anonymous>)
at C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework\JSFiles\testspec.js:8:71
at new Promise (<anonymous>)
at __awaiter (C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework\JSFiles\testspec.js:4:12)
at Suite.fdescribe (C:\Users\Admin\Eclipse Protractor
JavaScript\ProtractorTypeScriptCucumberFramework\testspec.ts:99:36)
Ran 1 of 5 specs
1 spec, 1 failure
Finished in 13.633 seconds
[12:36:37] I/launcher - 0 instance(s) of WebDriver still running
[12:36:37] I/launcher - chrome #01 failed 1 test(s)
[12:36:37] I/launcher - overall: 1 failed spec(s)
[12:36:37] E/launcher - Process exited with error code 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! protractortypescriptcucumberframework#1.0.0 test: `protractor JSFiles/configuration.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the protractortypescriptcucumberframework#1.0.0 test 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\Admin\AppData\Roaming\npm-cache\_logs\2020-07-21T07_06_38_712Z-debug.log
PS C:\Users\Admin\Eclipse Protractor JavaScript\ProtractorTypeScriptCucumberFramework>

Related

TypeError: JwtStrategy requires a secret or key

I've read the million threads with the same issue but I couldn't solve it :(
This is an old project I made and I need to access to it again but I'm getting the following error when running npm start:
> express-typescript-starter#0.1.0 start
> npm run tsc && npm run serve
> express-typescript-starter#0.1.0 tsc
> tsc
> express-typescript-starter#0.1.0 serve
> ts-node src/server.ts
{"level":"debug","message":"Logging initialized at debug level"}
C:\Users\alan_\Desktop\cdng\mern-finance-server-master\node_modules\passport-jwt\lib\strategy.js:45
throw new TypeError('JwtStrategy requires a secret or key');
^
TypeError: JwtStrategy requires a secret or key
at new JwtStrategy (C:\Users\alan_\Desktop\cdng\mern-finance-server-master\node_modules\passport-jwt\lib\strategy.js:45:15)
at Object.<anonymous> (C:\Users\alan_\Desktop\cdng\mern-finance-server-master\src\config\passport.ts:6:28)
at Module._compile (node:internal/modules/cjs/loader:1149:14)
at Module.m._compile (C:\Users\alan_\Desktop\cdng\mern-finance-server-master\node_modules\ts-node\src\index.ts:858:23)
at Module._extensions..js (node:internal/modules/cjs/loader:1203:10)
at Object.require.extensions.<computed> [as .ts] (C:\Users\alan_\Desktop\cdng\mern-finance-server-master\node_modules\ts-node\src\index.ts:861:12)
at Module.load (node:internal/modules/cjs/loader:1027:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12)
at Module.require (node:internal/modules/cjs/loader:1051:19)
at require (node:internal/modules/cjs/helpers:103:18)
at Object.<anonymous> (C:\Users\alan_\Desktop\cdng\mern-finance-server-master\src\app.ts:16:1)
at Module._compile (node:internal/modules/cjs/loader:1149:14)
at Module.m._compile (C:\Users\alan_\Desktop\cdng\mern-finance-server-master\node_modules\ts-node\src\index.ts:858:23)
at Module._extensions..js (node:internal/modules/cjs/loader:1203:10)
at Object.require.extensions.<computed> [as .ts] (C:\Users\alan_\Desktop\cdng\mern-finance-server-master\node_modules\ts-node\src\index.ts:861:12)
at Module.load (node:internal/modules/cjs/loader:1027:32)
This is src/config/passport.ts:
import passport from 'passport'
import { Strategy as JwtStrategy, ExtractJwt } from 'passport-jwt'
import userServices from '../services/userServices'
import { JWT_SECRET } from '../util/secret'
export const jwtStrategy = new JwtStrategy(
{
secretOrKey: JWT_SECRET,
jwtFromRequest: ExtractJwt.fromAuthHeaderAsBearerToken(),
},
async (payload: any, done: any) => {
const userEmail = payload.email
const foundUser = await userServices.findUserByEmail(userEmail)
done(null, foundUser)
}
)
When running "npm i" I'm getting a bunch of errors as well but I could --force it:
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: jest-config#27.5.1
npm WARN Found: ts-node#8.10.2
npm WARN node_modules/ts-node
npm WARN dev ts-node#"^8.6.2" from the root project
npm WARN
npm WARN Could not resolve dependency:
npm WARN peerOptional ts-node#">=9.0.0" from jest-config#27.5.1
npm WARN node_modules/jest-config
npm WARN jest-config#"^27.5.1" from #jest/core#27.5.1
npm WARN node_modules/#jest/core
npm WARN 1 more (jest-cli)
npm WARN
npm WARN Conflicting peer dependency: ts-node#10.9.1
npm WARN node_modules/ts-node
npm WARN peerOptional ts-node#">=9.0.0" from jest-config#27.5.1
npm WARN node_modules/jest-config
npm WARN jest-config#"^27.5.1" from #jest/core#27.5.1
npm WARN node_modules/#jest/core
npm WARN 1 more (jest-cli)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: ts-jest#26.5.6
npm ERR! Found: jest#27.5.1
npm ERR! node_modules/jest
npm ERR! dev jest#"^27.5.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer jest#">=26 <27" from ts-jest#26.5.6
npm ERR! node_modules/ts-jest
npm ERR! dev ts-jest#"^26.5.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: jest#26.6.3
npm ERR! node_modules/jest
npm ERR! peer jest#">=26 <27" from ts-jest#26.5.6
npm ERR! node_modules/ts-jest
npm ERR! dev ts-jest#"^26.5.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
You can see the whole repo here.
Thanks!
I'm not going to attempt to fix your conflicts, but npm i -force will allow everything to be installed.
You will also need to place a .env file in the root and ensure it has a JWT_SECRET secret value.
There are also a lot of other .env values required. Your .env should look like this (or production):
JWT_SECRET = 'jhagdhjwf'
MONGODB_URI = 'mongodb://localhost:27017/local'
PORT = 3000
CLOUD_NAME = 'Your cloud name'
CLOUDINARY_API_KEY = '123123123123'
CLOUDINARY_API_SECRET = 'abc123abc123abc123abc123'
NODE_ENV = 'production'
I don't know why you didn't think an .env was not required. I thought you said this was your project?
As you will also know, you have to have cloudinary API config and also a running mongodb server, on which you store your data.
Eg, install docker and run the command to get a quick running local version:
docker run -d -p 27017:27017 --name test-mongo mongo:latest
I did a pull of the code and everything works locally. Add this .env and it will work:
> express-typescript-starter#0.1.0 start
> npm run tsc && npm run serve
> express-typescript-starter#0.1.0 tsc
> tsc
> express-typescript-starter#0.1.0 serve
> ts-node src/server.ts
{"level":"debug","message":"Logging initialized at debug level"}
(node:78699) DeprecationWarning: collection.ensureIndex is deprecated. Use createIndexes instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
App running on port 3000
Opening http://localhost:3000/api/v1/users will give you the expected [] response. I assume you have a front end somewhere.
Everything should be working as expected.
Extra: Your import { JWT_SECRET } from '../util/secret' is not the right file name. In your repo it is https://github.com/AlanFPS/mern-finance-server/blob/master/src/util/seccret.ts. Your import is looking for secret but your file is called seccret (two c's).

npm error E401: Unable to authenticate, need: Basic realm="GitHub"

I have an issue with node v10.15.1 and npm v6.14.15
Running npm install into the root folder of a project, I have the following error:
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="GitHub"
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/myuser/.npm/_logs/2022-08-10T17_31_09_840Z-debug.log
The log file reports this:
2675 verbose stack Error: Unable to authenticate, need: Basic realm="GitHub"
2675 verbose stack at res.buffer.catch.then.body (/Users/myuser/.nvm/versions/node/v10.15.1/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:107:17)
2675 verbose stack at process._tickCallback (internal/process/next_tick.js:68:7)
2676 verbose statusCode 401
2677 verbose pkgid socket.io-client#https://github.com/substack/socket.io-client/tarball/master
2678 verbose cwd /Users/myuser/myproject
2679 verbose Darwin 20.6.0
2680 verbose argv "/Users/myuser/.nvm/versions/node/v10.15.1/bin/node" "/Users/myuser/.nvm/versions/node/v10.15.1/bin/npm" "install"
2681 verbose node v10.15.1
2682 verbose npm v6.14.15
2683 error code E401
2684 error Unable to authenticate, need: Basic realm="GitHub"
2685 verbose exit [ 1, true ]
I have other projects that compile perfectly with node v10.15.1 and npm v6.14.15
Any help will be appreciated.
Thanks
I solved this problem by myself.
If you have a similar issue, check in your npm configurations if you have the option always-auth=true, typing:
npm config list
In my case, I had :
; userconfig /Users/myuser/.npmrc
always-auth = true
In order to bypass this problem, create a .npmrc file in the root folder of your project and force the property to false:
always-auth = false
Now, npm config list should show you something like this:
; project config /Users/myuser/myproject/.npmrc
always-auth = false
With this configuration you should solve the E401 Basic realm="GitHub"

Azure Data Factory CI npm validate step suddenly crashing

We've been using the "new" CICD setup for Azure Data Factory as descibed by the documentation page: https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery-improvements. We're doing this using Azure DevOps pipelines written in YAML.
This has been working quite well for us, until it suddenly started crashing at the validation step this morning. No code has been changed on our side. I'm wondering if there's some issue with version number or incompatability but I can't find anything.
The Azure YAML code in question is this:
- task: Npm#1
displayName: 'Validate ADF json'
inputs:
command: 'custom'
workingDir: $(packageJsonFolder)
customCommand: 'run build validate $(Build.Repository.LocalPath)/DataFactories/${{ parameters.folderName }} $(adfAzureResourceId)'
The full log of error messages is as following:
node /home/vsts/work/1/s/DataFactories/downloads/main.js validate /home/vsts/work/1/s/DataFactories/internaldataload /subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx
/home/vsts/work/1/s/DataFactories/node_modules/#microsoft/azure-data-factory-utilities/lib/bundle.manager.js:53
throw "Execution failed with exit code: " + exitCode;
^
Execution failed with exit code: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # build: `node node_modules/#microsoft/azure-data-factory-utilities/lib/index "validate" "/home/vsts/work/1/s/DataFactories/internaldataload" "/subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # build 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! /home/vsts/.npm/_logs/2022-06-16T09_04_15_237Z-debug.log
=====ERROR=====
Error: Command failed: node /home/vsts/work/1/s/DataFactories/downloads/main.js validate /home/vsts/work/1/s/DataFactories/internaldataload /subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx
/home/vsts/work/1/s/DataFactories/downloads/main.js:2
(()=>{var e={82257:(e,t,r)=>{e.exports=r(53605)
at Object.94616 (/home/vsts/work/1/s/DataFactories/downloads/main.js:2:4897020)
at r (/home/vsts/work/1/s/DataFactories/downloads/main.js:2:7274976)
at /home/vsts/work/1/s/DataFactories/downloads/main.js:2:7275513
at /home/vsts/work/1/s/DataFactories/downloads/main.js:2:7953499
at Object.<anonymous> (/home/vsts/work/1/s/DataFactories/downloads/main.js:2:7953503)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
Execution finished....
Found npm debug log, make sure the path matches with the one in npm's output: /home/vsts/.npm/_logs/2022-06-16T09_04_15_237Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/opt/hostedtoolcache/node/10.24.1/x64/bin/node',
1 verbose cli '/opt/hostedtoolcache/node/10.24.1/x64/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build',
1 verbose cli 'validate',
1 verbose cli '/home/vsts/work/1/s/DataFactories/internaldataload',
1 verbose cli '/subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx' ]
2 info using npm#6.14.12
3 info using node#v10.24.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle #~prebuild: #
6 info lifecycle #~build: #
7 verbose lifecycle #~build: unsafe-perm in lifecycle true
8 verbose lifecycle #~build: PATH: /opt/hostedtoolcache/node/10.24.1/x64/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/vsts/work/1/s/DataFactories/node_modules/.bin:/opt/hostedtoolcache/node/10.24.1/x64/bin:/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin:/home/vsts/.local/bin:/opt/pipx_bin:/home/vsts/.cargo/bin:/home/vsts/.config/composer/vendor/bin:/usr/local/.ghcup/bin:/home/vsts/.dotnet/tools:/snap/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle #~build: CWD: /home/vsts/work/1/s/DataFactories
10 silly lifecycle #~build: Args: [ '-c',
10 silly lifecycle 'node node_modules/#microsoft/azure-data-factory-utilities/lib/index "validate" "/home/vsts/work/1/s/DataFactories/internaldataload" "/subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx"' ]
11 silly lifecycle #~build: Returned: code: 1 signal: null
12 info lifecycle #~build: Failed to exec build script
13 verbose stack Error: # build: `node node_modules/#microsoft/azure-data-factory-utilities/lib/index "validate" "/home/vsts/work/1/s/DataFactories/internaldataload" "/subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx"`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/opt/hostedtoolcache/node/10.24.1/x64/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (/opt/hostedtoolcache/node/10.24.1/x64/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid #
15 verbose cwd /home/vsts/work/1/s/DataFactories
16 verbose Linux 5.13.0-1029-azure
17 verbose argv "/opt/hostedtoolcache/node/10.24.1/x64/bin/node" "/opt/hostedtoolcache/node/10.24.1/x64/bin/npm" "run" "build" "validate" "/home/vsts/work/1/s/DataFactories/internaldataload" "/subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx"
18 verbose node v10.24.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 1
22 error # build: `node node_modules/#microsoft/azure-data-factory-utilities/lib/index "validate" "/home/vsts/work/1/s/DataFactories/internaldataload" "/subscriptions/xxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxx/providers/Microsoft.DataFactory/factories/xxxxx"`
22 error Exit status 1
23 error Failed at the # build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
##[error]Error: Npm failed with return code: 1
Finishing: Validate ADF json
Our package.json file is exactly as from the documentation page.
{
"scripts":{
"build":"node node_modules/#microsoft/azure-data-factory-utilities/lib/index"
},
"dependencies":{
"#microsoft/azure-data-factory-utilities":"^0.1.5"
}
}
Any ideas what we can do?
Fixed after updating the 'Install Node.js' task to match the reference from doc:
# Installs Node and the npm packages saved in your package.json file in the build
- task: NodeTool#0
inputs:
versionSpec: '14.x'
displayName: 'Install Node.js'

AssertionError [ERR_ASSERTION]: Host should not be empty at proxy in expressjs

i am trying to run expressjs project it's shows errors like
AssertionError [ERR_ASSERTION]: Host should not be empty at proxy (/../../Desktop/folder/myproject/node_modules/express-http-proxy/index.js:27:3)
{
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: true,
operator: '=='
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! authentication#1.0.0 start: ./node_modules/typescript/bin/tsc; node main
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the authentication#1.0.0 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! /home/folder/.npm/_logs/2020-01-01T07_03_08_044Z-debug.log
Your app is using proxy from express-http-proxy, proxy is supposed to take first argument as a value. That value is missing or undefined.
Check all the occurrence of proxy function inside your app and find the missing argument, most probably you have defined that value and taken from .env file but it's not define inside .env file.

Travis-CI build - PhantomJS error preventing QUnit tests from running

I have a repository with a simple js function and a QUnit test. I have attempted to integrate it with Travis-CI using a grunt task. Everything works fine locally but PhantomJS throws an error during the build process preventing my tests from running.
Build:
https://travis-ci.org/DaveKingsnorth/ciSandbox/builds/40909225
Repo:
https://github.com/DaveKingsnorth/ciSandbox
//.travis.yaml
language: node_js
node_js:
- "0.11"
before_install: npm install -g grunt-cli
install: npm install
// Gruntfile.js
module.exports = function(grunt) {
grunt.initConfig({
pkg: '<json:package.json>',
qunit: {
src: ['test/**/*.html']
}
});
grunt.loadNpmTasks('grunt-contrib-qunit');
grunt.registerTask('test', ['qunit']);
grunt.registerTask('default', 'qunit');
};
Error:
Testing test/index.html
PhantomJS threw an error:ERROR
/home/travis/build/DaveKingsnorth/ciSandbox/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom/bin/phantomjs: 4: /home/travis/build/DaveKingsnorth/ciSandbox/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom/bin/phantomjs: Syntax error: Unterminated quoted string 0 [ '/home/travis/build/DaveKingsnorth/ciSandbox/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom/bin/phantomjs: 4: /home/travis/build/DaveKingsnorth/ciSandbox/node_modules/grunt-contrib-qunit/node_modules/grunt-lib-phantomjs/node_modules/phantomjs/lib/phantom/bin/phantomjs: Syntax error: Unterminated quoted string' ]
Warning: PhantomJS exited unexpectedly with exit code 2. Use --force to continue.
Aborted due to warnings.
The command "npm test" exited with 0.
Done. Your build exited with 0.