Bump and pin dependencies per-release

Codes under work well some times before, but never worknow : try { autobahn = require('autobahn'); } catch (e) { console.log("wamp_orbital.js.connectServer exception = " +e); return; } Exception occurs:

wamp_orbital.js.connectServer exception = TypeError [ERR_NO_ICU]: “fatal” option is not supported on Node.js compiled without ICU

Since I didn’t meet such errors before, and I didn’t change any code, maybe there is some difference in node-version or Electron-version, but I forgot corrent ones.

node -v v12.10.0 electron 2.0.8

Anyone met the same problem as me?

[peterforgacs]

Thanks, this works with electron >= 4.0.0 but produces the same error on older electron versions.

In this case, this is caused by the cbor dependency increased the minimum required Node.js version in its latest stable version, which older electrons do not support.

This would not be a problem in itself, they follow semver. The problem is that autobahn only sets a minimum version requirement in the package.json. (>=)

This causes all clients to install the latest stable version of the dependency. And there is no guarantee that the latest stable version of the dependency Node.js requirement is in line with the specific electron Node.js version.

As a possible long term solution:

Can we fixate the concrete versions for the dependencies? Instead of cbor >= 3.0.0 cbor 3.0.0 etc. ( Same holds true for other dependencies )

This would make autobahn much more stable in electron in the long run.

Created a test repo to illustrate the problem here.

You can change the electron version and see how it behaves differently.

[oberstet]

Sounds great!

alright, then we’ll do that. changing issue label to enhancement …

Electron changed its versioning system about a year ago. … Changing the major version of big electron application requires quite lot of work.

thanks for explaining! understood & agreed