[Stage 1] Establish the v2 workspace and package baseline
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Tranquilla
- Stack tecnologico
- typescript
- Ambito
- build-system, devtools
Direzione di ricerca
Start by checking the completion status of prerequisite issues #315, #314, #313, #317, #312, and #316, then follow the seven execution steps in this issue. Work targets the v2 branch; use the package, build, release, and CI checks named in the exit criteria to verify each step. Done means all exit criteria pass, including an npm-installed 2.x prerelease under next that consumers can verify.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Goal
Establish the workspace, package, build, and prerelease baseline required for the v2 modular architecture without splitting public runtime features yet.
All Stage 1 work targets v2. During this stage, main remains the stable, maintenance-only v1 line. A relevant v1 change is synchronized manually according to #316.
At the end of this stage, the library lives in a pnpm workspace, development applications consume package boundaries, private implementation packages are bundled into public artifacts, and the v2 release workflow has published a consumer-verified 2.x prerelease under next.
Stage 1 starts after #315, #314, #313, #317, #312, and #316 are complete. It does not wait for release/v1 or final cutover.
Exit criteria
- pnpm is the only package manager used on v2 and clean installs use a frozen lockfile.
- The public @gravity-ui/graph package lives in packages/graph and can be packed independently.
- Every public entry point present at the approved split commit or added by an approved synchronized v1 contract change is preserved or intentionally migrated.
- Storybook and E2E are private workspace projects consuming public package entry points.
- Packed artifacts pass isolated vanilla JavaScript, React, and applicable Playwright consumer checks.
- Production artifacts and export maps are explicit and validated.
- The private scheduler workspace package is bundled into @gravity-ui/graph and absent from published dependencies.
-
release-v2.ymlpublishes fromv2using the monorepo package graph. - An approved
2.xprerelease is published undernextand installed successfully from npm. - No private workspace package is published or exposed as an unresolved runtime dependency.
- Package-boundary rules and CI prevent source-path bypasses.
- Drift from
mainis checked before the Stage 1 prerelease. - Every child issue leaves the library buildable, testable, and ready for the next migration step.
Execution order
- Adopt pnpm and verify the current root package tarball.
- Move @gravity-ui/graph into packages/graph.
- Extract Storybook and E2E into private workspace projects.
- Normalize the production build and export map.
- Extract the private scheduler package and prove inlining.
- Migrate and validate the v2 release workflow for the monorepo.
- Enforce workspace boundaries and finalize v2 CI gates.
Related
- #310
- #312
- #313
- #314
- #316
- #317
- #116
- Lingua principale
- TypeScript
- Stelle
- 145
- Fork
- 12
- Merge medio
- 1g 14h
- PR unite (30g)
- 43
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di gravity-ui/graph
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
gravity-ui/graph#457 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
gravity-ui/graph#455 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
gravity-ui/graph#456 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
gravity-ui/graph#431 ·
I maintainer di solito rispondono entro 1 giorno
-
proposal
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
gravity-ui/graph#416 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di gravity-ui/graph
Issue simili
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
openclaw/openclaw#199885 · 2 commenti · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
-
feature needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
BoardGamesEmpire/board-games-empire-backend#1306 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
sequant-io/sequant#1689 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100