Enable caching by default if packageManager
field is defined in package.json
#686
Labels
feature request
New feature or request to improve the current logic
Description:
The action allows caching global packages data as per documentation in https://github.com/actions/setup-node#caching-global-packages-data
It's an amazing feature and reduces action execution time, but it has to be enabled in configuration.
Caching is not enabled in default setup. Users may not discover caching feature by default, and miss on the faster executions times enabled by caching.
The feature request is to enable caching by default if
packageManager
field is defined.This can be enabled in a major version bump, say
v4
, to not affect existing users.Justification:
Just want all users to get benefit of faster executions times allowed by caching without explicitly opting in, if they have set up packageManager field in their package.json
They can always explicitly opt-out by setting
cache
to empty string.Are you willing to submit a PR?
Yes
The text was updated successfully, but these errors were encountered: