toolkit merge: Phase B — extract @sentry/toolkit-core (shared code)

Open
#1,247 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript

Research direction

Read the linked Phase B plan, especially §7, and inspect the existing property/model-based tests that are named as the safety net. Map the five listed shared surfaces and their current seams before choosing one extraction. Done means the shared code is incrementally behind a workspace dependency with the existing tests still passing.

Written by the indexing model from the issue text.

Description

Sub-task of the toolkit monorepo merge (master issue linked below). Plan: https://gist.github.com/BYK/8c0ce6cec64608f41fe5654b7827228e

Phase B (fast-follow): extract @sentry/toolkit-core. Incrementally move
shared surfaces behind a workspace dep, one seam at a time, with existing
property/model-based tests as the safety net:

  • Sentry API client + auth/OAuth device flow + token storage.
  • Region detection / multi-region fan-out.
  • Shared Zod types (issues/events/projects/orgs).
  • Telemetry setup + error taxonomy.
  • Agent-skill generation / plugin-marketplace machinery.

This is where the long-term ROI of the merge is realized. See §7.

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.