Closed travi closed 1 year ago
Uh oh! cc/@giltayar
Yup. It's a bug in Node.js 16.13.x
, fixed in 16.14.x
. Node.js doesn't pass me the "message port" through which the API and the loader communicate.
While I could use the old system that didn't use a message port, specifically only for Node.js 16.13.0
, I don't think it's worth it.
Thanks for the reproduction, though! It's issues like these that make our life easier!
understood. unfortunate that this means that i'll need to push out some major package versions in order to get updated, but i totally understand the stance. thanks for the explanation
i'm excited about the update to support node v20, so i'm eager to get recent renovate PRs for the new testdouble version merged. however, some of my projects are failing for those updates when i have node v16.13.0 in the matrix of versions. it looks like v16.14.0 is passing, but v16.12.0 fails like v16.13.0. I did not test more versions below v16.12.0.
an example of the error that i'm seeing can be found in this build result.
reproduction steps:
git clone git@github.com:form8ion/project.git
nvm use 16.13.0
npm install
npm run test:integration