Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse package.json from subfolder #83

Closed
some-user123 opened this issue May 23, 2023 · 1 comment
Closed

Parse package.json from subfolder #83

some-user123 opened this issue May 23, 2023 · 1 comment

Comments

@some-user123
Copy link

some-user123 commented May 23, 2023

My package.json is not located at top level but in a subfolder at ui/package.json.
This is not picked up by this action.

Error: Error: ENOENT: no such file or directory, open '/home/runner/work/$repo/$repo/package.json'

actions/setup-node allows to explicitly define the path, e.g.

with:
  node-version-file: 'ui/package.json'
  cache: pnpm
  cache-dependency-path: ui/pnpm-lock.yaml

It would be nice to have something similar for this action, e.g.

with:
  pnpm-version-file: 'ui/package.json'

Setting the working-directory does not work.

defaults:
  run:
    working-directory: ./ui
therealvio added a commit to therealvio-org/ralphbot that referenced this issue May 29, 2023
The pnpm/setup-pnpm github action does not support specifying
subdirectories to allow the action to consult the package.json file's
packageManager property. This means that the `pnpm` version needs to be
specified manually until support has been added.

Renovate can update this as part of a regexManager configuration. This
should enable `pnpm` updates to be done altogether, rather than
staggered.

- Open Issue: pnpm/action-setup#83
@KSXGitHub
Copy link
Collaborator

v2.3.0 has been released. You may check if it work properly.

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

No branches or pull requests

2 participants