Automattic / Automattic/studio
Feature Request: better workspace experience
- Dominant language
- TypeScript
- Stars
- 517
- Forks
- 95
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 162
Description
### What
Hi,
I'm sorry to open an issue, i would prefer a discussion.
I went over your project and i'm wondering if my tool could improve your developer and CI experience.
It's a Node.js CLI to orchestrate npm workspaces test scripts with features like fail fast mode, concurrent execution, cold/hot change detection and more. The goal is to create a better feedback loop for large monorepos organized with npm workspaces.
### Why
npm workspaces are executed sequentially and lack of usefull features for large monorepositories like fail fast mode, topological sort etc, asked by the community and already present in other package managers like pnpm or yarn.
### How
the website: [Sumlyzer](https://github.com/ErwanRaulo/sumlyzer)
Would you want to try ? if no, i would be glad to get your insights about it.
Erwan (a french software engineer).
Contributor guide
Research direction
Start by reviewing the Sumlyzer project linked in the issue and compare its workspace orchestration features with WordPress Studio's stated desktop and CLI workflow. The issue names no Studio file, test, or entry point, and it does not define an integration scope or acceptance criteria, so the completed work is not yet clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100