Support nodejs debug build
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
Description:
Support using a debug and asan build of nodejs thru this action.
See https://github.com/nodejs/node/blob/main/BUILDING.md#building-a-debug-build and https://github.com/nodejs/node/blob/main/BUILDING.md#building-an-asan-build
Justification:
Especially when dealing with packages using native code, debugging a bug in a nodejs application can require inspecting native stack traces and having better debuggability at the native layer.
Example usecase:
- You run your unit tests in CI, you start semi-consistently getting segfaults. (eg: https://github.com/ChainSafe/lodestar/actions/runs/6811279841/job/18521433662#step:6:1598)
- You now use use the debug build of nodejs to help debug the segfault
Are you willing to submit a PR?
Possibly? If a maintainer can help point out what to do at a high level, I'm willing to spend a few hours.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the action's current Node.js setup flow and the linked Node.js BUILDING.md sections for debug and ASAN builds. Compare the requested behavior with the example CI failure, then determine how the action should expose or select these builds; done means both build types can be used through the action and are covered by validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100