Description
Checklist
- I have looked into the Readme and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Description
As seen on the README file at GitHub, the circleci run fails. It appears that the culprit is likely line 11 of .circleci/config.yml. I have been able to progress beyond the point at which the master source build becomes stuck. Mine fails much later on because the circleci build is updating the version of node to one that is not supported by the [email protected] that was published to npmjs just two days ago, or by the previous version either. Regardless of the version of node that I specify, it gets updated to 23.10.
There was a report related to this in the Auth0 Community forums at Community Forum Report. The messages on that report promised compatibility with Node 22 by Q1 of 2025. That promise appears to have been kept two days ago, but in the meantime the default version of Node used in the circleci build has advanced to Node 23, as seen in my screenshot of the circleci error.
Reproduction
Additional context
It seems like the circleci/node used could advance from 5.0.2 to 7.1.0 and that the docker image used should be specified by version (such as 22.10 or 20.2.0 for initial compatibility with node-oauth2-jwt-bearer, as I have tried with my fork), but the node version doesn't stay put anyway.
Which browsers have you tested in?
Edge