[Stage 1] Establish the v2 workspace and package baseline

未关闭
#318 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 小时
30 天内合并 PR
43

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

gravity-ui/graph 的其他 Issue

查看 gravity-ui/graph 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。