bug: about jose HOT 6 CLOSED

This is not a bug, it's just an ES Next language feature not available to older node versions. You can see [email protected] has a runtime requirement of node >=12.0.0 right in the readme.

You can also see extensive CI of both projects

• https://github.com/panva/jose/commit/eeb4ab56a11feb750562e323b580d87b7b061f08/checks
• https://github.com/panva/node-oidc-provider/commit/627e9aa7679832ba90387105c01daa6db9b28435/checks

from jose.

Ah, I see. I hadn't seen that syntax before. Sorry for the bad issue.

from jose.

No problem.

Node >=12.0.0 is the described minimal version in both projects README's as well as package.json (so during npm/yarn install you must've omitted a warning). It is for its KeyObject and crypto module additions that are only available in the Node 12 trackk. This new private class fields syntax is just something which i’m glad to have available as a side effect.

from jose.

#37 https://v8.dev/features/class-fields

from jose.

I've made @panva/jose compatible with lts/dubnium, it is now being tested with Node.js ^10.13.0 || >=12.0.0 and Electron ^6.0.0

It is not without caveats, but they are acceptable.

• Importing X.509 certificates and handling x5c is only supported when Node.js >= 12.0.0 runtime is detected
• OKP keys are only supported when Node.js >= 12.0.0 runtime is detected

from jose.

Cool, sounds great, thanks! I think supporting active LTS versions of node is a great idea. In my particular case, upgrading to node 12 wasn't a problem, so I upgraded our project to node 12.x and both oidc-provider and @panva/jose have been working great. 👍

from jose.