Repository navigation
[v8] Merge @sentry/utils into @sentry/core #9832
Description
In v8, let's merge utils into core, so all shared, runtime agonstic things are in utils, while runtime specific things should be moved out of utils into either browser or server-runtimes packages.
If we have things that are e.g. browser specific that are needed by e.g. replay or feedback packages, we need to see what we do with them. But either we create a new e.g. browser-utils package for this (if needed) or, if it's not a lot, we just duplicate stuff a bit - we'll need to see case-by-case if this is necessary.
### Tasks
- [ ] https://github.com/getsentry/sentry-javascript/pull/11381
- [ ] https://github.com/getsentry/sentry-javascript/pull/11451
- [ ] Move rest of imports into @sentry/core or @sentry/node
- [ ] Delete utils package
Activity
feat(v8/utils): Remove deprecated util functions (#11143)
feat: Add @sentry-internal/browser-utils (#11381)
ref(browser): Move utils to @sentry-internal/browser-utils (#11451)
AbhiPrasad commentedon Apr 8, 2024
Given we have moved all browser related code into the browser utils package, this can be considered done.
We can now review on a more case-by-case basis if we should move functions from utils
feat(v8/utils): Remove deprecated util functions (getsentry#11143)
feat: Add @sentry-internal/browser-utils (getsentry#11381)
ref(browser): Move utils to @sentry-internal/browser-utils (getsentry…
mydea commentedon Apr 22, 2024
we did part of this, the rest we may do in v9 (or not...)