To prevent accidental upgrades to a new (and very incompatible) version of swagger-ui, I am proposing to add an explicit version check that will abort the test suite when upgrade is detected.
$ npm t
> loopback-component-explorer@6.3.1 test /Users/bajtos/src/loopback/component-explorer
> mocha
Upgrading from swagger-ui@2 to a newer major version is difficult, see
https://github.com/strongloop/loopback-component-explorer/issues/254
If you are confident about this change and have manually verified API Explorer
functionality in the browser, including access-token based authentication,
then you can delete this check.
npm ERR! Test failed. See above for more details.
To prevent accidental upgrades to a new (and very incompatible) version of swagger-ui, I am proposing to add an explicit version check that will abort the test suite when upgrade is detected.
See #250, #253 and and #254.