pnpm workspace support

Open
#892 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
build-system, tooling

Research direction

Start by reproducing the CI cleanup error involving pnpm-lock.ember-try.yaml and trace the scenario cleanup path that attempts to stat it. Compare the pnpm workspace behavior with the existing workspace handling, including whether yarn is affected. Done means the cleanup completes without the ENOENT message while the relevant CI scenarios still pass.

Written by the indexing model from the issue text.

Description

Largely works but this error is consistently printed in CI indicating incomplete cleanup. Jobs work and this error does not cause the scenario to fail, but figured I'd put this here for a cleanup pass later. This may apply to yarn workspaces as well?

Error cleaning up scenario: [Error: ENOENT: no such file or directory, stat '/home/runner/work/data/data/tests/main/pnpm-lock.ember-try.yaml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'stat',
  path: '/home/runner/work/data/data/tests/main/pnpm-lock.ember-try.yaml'
}
Dominant language
JavaScript
Stars
180
Forks
57
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ember-cli/ember-try

All issues in ember-cli/ember-try

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.