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

task(workspaces): update exec #288

Closed
3 tasks done
darcyclarke opened this issue Mar 2, 2021 · 0 comments · Fixed by npm/cli#2886
Closed
3 tasks done

task(workspaces): update exec #288

darcyclarke opened this issue Mar 2, 2021 · 0 comments · Fixed by npm/cli#2886
Assignees

Comments

@darcyclarke
Copy link
Contributor

darcyclarke commented Mar 2, 2021

Exit criteria

  • exec should be able to operate/iterate against a set of defined workspaces
  • Tests are written validating this behavior
  • Documentation is updated to reflect this change (ex. metadata/label showing the degree of workspace support)
@darcyclarke darcyclarke added this to the OSS - Sprint 25 milestone Mar 2, 2021
ruyadorno added a commit to ruyadorno/cli that referenced this issue Mar 17, 2021
Add workspaces support to `npm exec`
  - Refactored logic to read and filter workspaces into
  `lib/workspaces/get-workspaces.js`
  - Add ability to execute a package in the context of each
  configured workspace

Fixes: npm/statusboard#288
ruyadorno added a commit to ruyadorno/cli that referenced this issue Mar 19, 2021
Add workspaces support to `npm exec`
  - Refactored logic to read and filter workspaces into
  `lib/workspaces/get-workspaces.js`
  - Added location context message when entering interactive
  shell using `npm exec` (with no args)
  - Add ability to execute a package in the context of each
  configured workspace

Fixes: npm/statusboard#288
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

Successfully merging a pull request may close this issue.

2 participants