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
Currently, available options of withastro/action@v2 is a subset of those of actions/setup-node@v4.
For example, node-version-file is not available.
In my usecase, I define Node.js as engines.node in package.json.
If I use actions/setup-node@v4 directly, I can specify node-version-file so that it reads the property.
Without this option, I have to manually sync Node.js versions in 2 files, workflow YAML file and package.json.
By the way, pnpm/action-setup@v3 automatically detects package manager and its version based on packageManager property in package.json, if package-manager of withastro/action@v2 is not specified, which enables me to manage package manager version in one place.
It may be fine to support other options of actions/setup-node@v4 too.
The text was updated successfully, but these errors were encountered:
Currently, available options of
withastro/action@v2
is a subset of those ofactions/setup-node@v4
.For example,
node-version-file
is not available.In my usecase, I define Node.js as
engines.node
inpackage.json
.If I use
actions/setup-node@v4
directly, I can specifynode-version-file
so that it reads the property.Without this option, I have to manually sync Node.js versions in 2 files, workflow YAML file and
package.json
.By the way,
pnpm/action-setup@v3
automatically detects package manager and its version based onpackageManager
property inpackage.json
, ifpackage-manager
ofwithastro/action@v2
is not specified, which enables me to manage package manager version in one place.It may be fine to support other options of
actions/setup-node@v4
too.The text was updated successfully, but these errors were encountered: