node-gradle / node-gradle/gradle-node-plugin

Corepack & Gradle 9

Open
#351 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Groovy
Stars
677
Forks
120
PR merge metrics
No merged PRs in 30d

Description

Hey,

I just wanted to open an issue because I'm currently maintaining my own personal fork of node-gradle in order to add gradle 9 support, as well as support for corepack (#342): https://github.com/solonovamax/gradle-node-plugin/

it's not currently in a condition where I'd feel comfortable PRing it, but it was enough for my usecase.
if you wanted to pull those commits into node-gradle, I'd be more than happy to help with that.
I've based my fork on the update-node-version and update-node-version branches.

Support for corepack was actually relatively straightforward. it seems that you can basically just prefix the command with corepack, and then it Just Works™
e.g. instead of doing pnpm install, you do corepack pnpm install

the one thing that was just rather annoying was fixing the mocking for ExecOperations:
https://github.com/node-gradle/gradle-node-plugin/commit/b0a4b48a703637b5e57afc516f0556106de7059c#diff-3e86f30a7042837bd17d78bacc8469493ef25f4b0037fe2a2ddb2e841dd2ab6cL27-R33

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked fork and commit b0a4b48, especially the ExecOperations mocking changes, then compare those changes with the current node-gradle implementation. Done means node-gradle supports Corepack and Gradle 9, with the relevant mocking and behavior covered by the project’s tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy, nodejs
Domain
build-system, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.