node-gradle / node-gradle/gradle-node-plugin
Bun cleanup
Open
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 677
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
- Verify the tests
- Verify that the tests actually test bun
- Check that the test cases use either a downloaded or local copy of bun
- Use the same bun version in tests that download bun
- Verify manually that
download = truebun works - Verify manually that
download = falsebun works - Check if anything from
BunExecRunnercan be shared between the other ExecRunners - BunxTask accidentally uses
npx
Extracted from https://github.com/node-gradle/gradle-node-plugin/issues/290#issuecomment-1774057375
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
Locate BunExecRunner, BunxTask, and their associated tests first. Check whether the tests cover both downloaded and local Bun versions, then verify both download modes manually and assess whether runner behavior can be shared. Done means every checklist item is verified and the BunxTask issue is confirmed resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, groovy
- Domain
- build-system, testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100