Ability to set Corepack version

[v1nc3n4]

Node.js/Corepack bundles provided in Node.js distributions frequently suffer from bugs that avoid installing package manager or dependencies, and lead to failures when task installFrontend is executed. As a end-user, it is difficult to identify the causes of such failures, and how to work around them quickly (this issue for example).

The plugin could provide a property allowing the end-user to replace the Corepack release bundled by default in the Node.js distribution with another one (typically the latest). A new task installCorepack could use this property to update Corepack release.

DSL

frontend {
    // may be null (by default), or "latest", or a concrete version number
    corepackVersion.set("latest")
}

Task installCorepack

• Dependency graph: installPackageManager -> installCorepack -> installNode
• Skippable: if corepackVersion is null
• Inputs: Property<String> corepackVersion
• Outputs: DirectoryProperty <nodeInstallDirectory>/node_modules/corepack

[MBelniak]

Yes! I'd love to use COREPACK_NPM_REGISTRY, but it's not there in the currently used version of corepack yet. I wish I could set the version of corepack to something newer.

[v1nc3n4]

Hi @MBelniak,

Thank you for using the plugin and your feedback.
I'm not sure I can deal with this new feature before March 2024. You may look at this comment for
a workaround until the feature is released.

BR

[MBelniak]

I switched to gradle-node-plugin instead :p

[v1nc3n4]

Great! I wish you can choose the version of Corepack with a simple configuration option if this feature exists with this plugin. Otherwise, feel free to get in touch with next releases here.

BR