[Stage 1] Establish the v2 workspace and package baseline

オープン
#318 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
静か
技術スタック
typescript

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.yml publishes from v2 using the monorepo package graph.
  • An approved 2.x prerelease is published under next and 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 main is checked before the Stage 1 prerelease.
  • Every child issue leaves the library buildable, testable, and ready for the next migration step.

Execution order

  1. Adopt pnpm and verify the current root package tarball.
  2. Move @gravity-ui/graph into packages/graph.
  3. Extract Storybook and E2E into private workspace projects.
  4. Normalize the production build and export map.
  5. Extract the private scheduler package and prove inlining.
  6. Migrate and validate the v2 release workflow for the monorepo.
  7. Enforce workspace boundaries and finalize v2 CI gates.

Related

  • #310
  • #312
  • #313
  • #314
  • #316
  • #317
  • #116
主要言語
TypeScript
スター
145
フォーク
12
平均マージ
1日 14時間
マージ済み PR(30日)
43

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

gravity-ui/graph のほかの issue

gravity-ui/graph の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。