README Studio section still documents the old npx serve launcher
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- documentation
Research direction
The outdated instructions are at README.md lines 237-238. Read docs/studio-v2-architecture.md around line 40, then install.sh near line 658 and scripts/studio-service.sh to confirm the orchestra-studio command and port 3110. Done when the README Studio section describes orchestra-studio on port 3110 and the npx serve commands are removed or marked as legacy.
Written by the indexing model from the issue text.
Description
Context
The README Studio section tells users to run npx serve on the built dist, but the Studio v2 architecture doc says that launcher was replaced by server/studio-api.js launched via orchestra-studio.
Evidence
README.md:237-238:npx serve -l 0 ~/.config/opencode/studio/dist/ Cursor variant.docs/studio-v2-architecture.md:40: "replacing the oldnpx servestatic launcher".install.sh:658launcher shim delegates toscripts/studio-service.sh.- Related: see the Cursor studio dist path issue.
Acceptance criteria
- README Studio section describes
orchestra-studioand port 3110. - Remove or mark the
npx serveinstructions as legacy.
Found during the v3.8.0 audit (tag v3.8.0, commit 22d2146). Paths/lines are at that commit.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from P-Core-System/pcore-orchestra
-
documentation good first issue priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
P-Core-System/pcore-orchestra#37 ·
Maintainers usually reply within 6 days
-
documentation good first issue priority: low
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
P-Core-System/pcore-orchestra#36 ·
Maintainers usually reply within 6 days
-
documentation good first issue priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
P-Core-System/pcore-orchestra#33 ·
Maintainers usually reply within 6 days
-
enhancement good first issue installer priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
P-Core-System/pcore-orchestra#20 ·
Maintainers usually reply within 6 days
-
enhancement good first issue installer priority: medium windows
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
P-Core-System/pcore-orchestra#18 ·
Maintainers usually reply within 6 days
All issues in P-Core-System/pcore-orchestra
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ImranR98/apps.obtainium.imranr.dev#2000 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
microsoft/monaco-editor#5577 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
obsidianmd/obsidian-help#1169 ·
Maintainers usually reply within 2 days
-
[docs] RELEASE.md: wrong branch name, no check that the prepare PR merged with the right subject, manual publish stepPossibly taken @albertteoh claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jaegertracing/jaeger-ui#4739 ·
Maintainers usually reply within 1 day