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.
Currently, available options of
withastro/action@v2is a subset of those ofactions/setup-node@v4. For example,node-version-fileis not available.In my usecase, I define Node.js as
engines.nodeinpackage.json. If I useactions/setup-node@v4directly, I can specifynode-version-fileso that it reads the property. Without this option, I have to manually sync Node.js versions in 2 files, workflow YAML file andpackage.json.By the way,
pnpm/action-setup@v3automatically detects package manager and its version based onpackageManagerproperty inpackage.json, ifpackage-managerofwithastro/action@v2is 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@v4too.