npm i fails on linux/s390x architecture

[virkt25]

Description/Steps to reproduce

loopback$ npm i

> [email protected] install /home/tleah/loopback/node_modules/phantomjs-prebuilt
> node install.js

PhantomJS not found on PATH
Unexpected platform or architecture: linux/s390x
It seems there is no binary available for your platform/architecture
Try to install PhantomJS globally
npm WARN [email protected] requires a peer of ajv@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of eslint@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of chai@^4.0.0 but none is installed. You must install peer dependencies yourself.
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":"linux","arch":"s390x"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node install.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] 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!     /home/tleah/.npm/_logs/2018-09-05T15_57_01_179Z-debug.log

CloudNativeJS tests projects against different architectures and currently we fail on linux/s390x because of phantomjs install failing. It's only needed for tests so isn't an accurate representation as LoopBack works find on this architecture.

There was an attempt to address this issue by skipping this dependency in this PR #3962 but it doesn't fully address the issue at hand.

Expected result

Test suite passes (excluding tests requiring phantomjs).

Additional information

[virkt25]

Released v 3.22.3 which only attempts to install phantomjs on supported architectures. Waiting on confirmation from cloudnativejs to see if the issue is now resolved.

[virkt25]

Verified as fixed.