getsentry / getsentry/sentry-javascript

Clean up utils/types-hoist folders from v9 migration

Open
#14,922 1 comment 0 reactions 0 assignees View on GitHub
Task
Dominant language
TypeScript
Stars
8.7k
Forks
1.8k
Avg merge
1d 17h
Merged PRs (30d)
523

Description

### Description

For v9 we hoisted `@sentry/utils` and `@sentry/types` into `@sentry/core`. We did that in a bit of a "lazy" way by dumping everything in a `utils-hoist` and `types-hoist` folder respectively and doing `export * from ...`.

Since `export * from ...` is rather error prone and makes bundlers unhappy because it makes them go look for exports, we should get rid of this patterns sooner rather than later and top-level-export all the api we intend to export.

Contributor guide

Open the contributing guide

Research direction

Inspect the @sentry/core package and its utils-hoist and types-hoist folders to inventory the current re-exports. Determine which APIs are intended to remain public, then replace the wildcard exports with explicit top-level exports and remove the hoist folders. Done means the intended APIs are exported without the existing wildcard pattern.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.