Open tlylt opened 1 year ago
Weird, it worked three years ago - maybe see what is being installed in npx via a verbose/debug flag?
Thanks @orta for following up! I just tried adding the --verbose flag, that gave more details from the danger execution:
npx danger-ts --verbose
Node.js v18.14.1
Failing the build, there is 1 fail.
Request failed [403]: https://api.github.com/user
Response: {
"message": "Resource not accessible by integration",
"documentation_url": "https://docs.github.com/rest/reference/users#get-the-authenticated-user"
}
Request failed [403]: https://api.github.com/user
Response: {
"message": "Resource not accessible by integration",
"documentation_url": "https://docs.github.com/rest/reference/users#get-the-authenticated-user"
}
Feedback: https://github.com/tlylt/danger-demo/pull/2#issuecomment-1435437361
Danger: ⅹ Failing the build, there is 1 fail.
## Failures
`node` failed.
## Markdowns
### Log
```sh
This suggests that it could be due to the node version. I found out that v18 and v16 result in the error above. However, v14 still works.
Not too sure what it takes to make it compatible with the latest versions though. Thanks.
Probably that 16 + 18 use different versions of npm and maybe it has different rules (I don't use npm anywhere) maybe there's a way to use yarn to trigger danger ts instead via yarn dlx
which is consistent across builds
Hi there!
I'm trying out the example given in the README, with slight modifications to use the latest
actions/checkout
andactions/setup-node
The result is a CI run failure: