You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make default npm project path configurable via taskfile variable
A repository might contain multiple npm-managed projects. For this reason, the appropriate npm-managed tasks have a
parameter environment variable that allows it to be configured for an arbitrary path, with the "Check npm" workflow
having a job matrix of paths to pass.
Generally, even if there are multiple npm-managed projects, there will be one primary project that is most often the
target of contributor operation. Since it would be inconvenient for the contributor to pass the environment variable
path every time they want to run a task for that primary project, the tasks are configured to have a default path which
is used if the variable is not defined by the user.
Since the primary npm-managed project would typically be in the root of the repository, the default value is set to the
root. In the case where the primary npm-managed project is not in the root of the repository, the template installer
will need to adjust this. Previously the default was hard coded in each individual task. The template will be made
easier to install by defining the default in a single place via a friendly taskfile variable, following the convention
already established by the templates for Go-based projects.
0 commit comments