After install node-red-contrib-swagger, the node list could not be displayed

[wangzhidong]

I'm using the NodeJS v6.11.2, and installed the node-red 0.17.5, the I run
npm install node-red-contrib-swagger
to install node-red-contrib-swagger.
But After installing, restart the node-red, all the components in leftside can't be displayed?
Anything wrong?

[bigdoods]

I can report the same behaviour. Console error;

Uncaught SyntaxError: Unexpected token <
    at eval (<anonymous>)
    at vendor.js:2
    at Function.globalEval (vendor.js:2)
    at text script (vendor.js:5)
    at Pb (vendor.js:5)
    at x (vendor.js:5)
    at b (vendor.js:5)
    at Object.send (vendor.js:5)
    at Function.ajax (vendor.js:5)
    at Function.m._evalUrl (vendor.js:5)

node v8.1.4
node-red latest commit e09efba313ab8724fd03cbb8cc22e26dd7663f6b

[marcostrullato]

Same issue here. Nodes disappear...

[adnmanai]

Hello any solution or news about this issue. Thank you

[beneuto]

Same. Node-red 0.18.4. Node 8.10.
Also, previous manual installed (in "nodes" directory) node broken after install of this node.

[t-beckmann]

The last version published to NPM is broken. It attempts downloading a file swagger/swagger.js which does not exist. The result is an HTML stating that file does not exist, but it is nevertheless attempted to be evaluated as JavaScript code. Therefore the error about unexpected token <.

The thing can be installed by

> npm i browserify
> npm i kmi/node-red-contrib-swagger#master

The first command installs browserify which is required for the postInstall step and is a missing dependency. The second command installs the master of this repo.

[NicoJuicy]

Could this be fixed with pushing an update to npm?

• The version on npm is 0.32 ( and doesn't support swagger 2)
• The version here on github is 0.4 ( and supports swagger 2)

Also note:
When going from the npm package to source, i had to start a node-red from scratch to make it work. Swagger is not found anymore in the modules.