New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
don't know how to turn this value into a node at valueToNode (node_modules/@babel/types/lib/converters/valueToNode.js:98:9) #263
Comments
some of the Babel packages were patched from .16 to .17 The issue is comming from this package: https://www.npmjs.com/package/@babel/types Could it be the cause? |
I was able to reproduce the issue locally with node v14.18.2 or v.17.4.0 so I can say it is not a node version issue, nor a problem with github actions. Also, nor a problem with our repo, since these testss passed on our last merge to our main branch. Im almost sure that this update on Babel broke everything. |
It looks like your stacktrace has a reference to |
@nolanlawson I need to upload coverage on codecov.io. so can't disable it. Maybe you could force babel core to stay at this version until you make this package compatible with babel 7.17? At the moment I think it is using ^ in the package and this allowed it to be bumped to 7.17 which broke the test. |
Could you run
|
OK thanks. Yes, it looks like This probably needs some more testing, but it may be an issue with the repo for |
Hm, updating all the dependencies in There is probably some specific combination of dependency versions that's causing this issue. |
I was able to reproduce the same issue in a fresh SFDX project: https://github.com/pmdartus/sfdx-jest-instanbul-bug. Update: This is a known jest issue. This issue is caused by babel/babel#14209, breaking Istanbul source map serialization. The Instanbul and Babel teams are currently working on fixing this issue (istanbuljs/istanbuljs#576). There is, unfortunately, nothing we can do at |
Description
I started to have this problem inside Github Actions
It started 18h ago +-, without any changes to the pipeline, dev dependencies, or even jest config files.
Another weird thing is that I can run all the tests on my machine with no problem. I even did a fresh install to simulate what happens in Github to ensure I was not using cached dependencies.
So it does not seem to be a problem with the dev dependencies, but I can't determine it for sure. That is why Im here asking for help.
my system info => all tests are executed with no problem
github actions info (we are using a docker image based on node:latest)
OBS: None of the following files were changed and the tests started failing. They fail only inside github actions. Locally I can run them without a problem.
jest-setup.js
jest.config.js
package.json
The text was updated successfully, but these errors were encountered: