Skip to content

Conversation

@labkey-susanh
Copy link
Contributor

@labkey-susanh labkey-susanh commented Jul 2, 2025

Rationale

Issue 53067 At some point, Gradle started to not like it when tasks shared output directories and it will not cache the task output when this happens, resulting in much more running of tasks than is strictly necessary. The wrapper tasks npmRunBuild and npmRunBuildProd are really more for convenience than anything, and do not need to declare explicit inputs or outputs since the output is produced by the wrapped tasks that come from the NPM plugin.

Related Pull Requests

Changes

  • Remove input and output configuration for wrapping tasks.

…declare outputs as they duplicate the wrapped tasks causing caching to be disabled
@labkey-susanh labkey-susanh merged commit 18e34ec into develop Jul 3, 2025
3 checks passed
@labkey-susanh labkey-susanh deleted the fb_npmTaskCaching branch July 3, 2025 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants