-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate and remove parseUrl
and refactor getSanitizedUrlString
#15767
Labels
Package: core
Issues related to the Sentry Core SDK
Comments
This was referenced Mar 21, 2025
AbhiPrasad
added a commit
that referenced
this issue
Mar 25, 2025
While working on #15767 I ran into a `parseUrl` function defined in `packages/browser-utils/src/instrument/xhr.ts`. This usage is fine, but was a bit confusing, so I renamed the method and expanded the docstring. I also expanded the types a little bit.
It's super annoying to remove I'm gonna try to solve this a different way. |
AbhiPrasad
added a commit
that referenced
this issue
Apr 1, 2025
The bottleneck of many of the tasks written down in our Node SDK performance improvement task #15861 is `parseUrl`, defined here: https://github.com/getsentry/sentry-javascript/blob/3d63621714b31c1ea4c2ab2d90d5684a36805a43/packages/core/src/utils-hoist/url.ts#L17 We created #15767 to track removal of `parseUrl`. See more details in the GH issue. While working on tasks for #15767, I initially PR'd #15768, which introduced a `parseStringToURL` method as a replacement for `parseUrl`. While trying to implement that method though I realized `parseStringToURL` has a lot of downsides. This PR removes `parseStringToURL` in favor of a new `parseStringToURLObject`. Given `parseStringToURL` was never exported by the core SDK, this is not a breaking change. To understand `parseStringToURLObject`, let's first look at it's method signature: ```ts function parseStringToURLObject(url: string, urlBase?: string | URL | undefined): URLObject | undefined ``` `parseStringToURLObject` takes a string URL and turns it into a `URLObject`, that is typed like so: ```ts type RelativeURL = { isRelative: true; pathname: URL['pathname']; search: URL['search']; hash: URL['hash']; }; type URLObject = RelativeURL | URL; ``` the JavaScript URL built-in does not handle relative URLs, so we need to use a separate object to to track relative URLs. Luckily it's pretty small surface area, we only need to worry about `pathname`, `search`, and `hash`. For ease of usage of this function, I also introduced a `isURLObjectRelative` helper. This will make sure that users can handle both relative and absolute URLs with ease. Given `packages/core/src/fetch.ts` was using `parseStringToURL`, I refactored that file to use `parseStringToURLObject`. The change feels way better to me, much easier to read and understand what is going on.
landed in a decently elegant solution for relative urls: #15882 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Now that we support ES2020 (aka not IE11 anymore) and Node.js 18+, we can get rid of
parseUrl
in favor of a method that just uses the built-in URL object. This will save us some bundle size (given we can remove that regex), and we get performance benefits from using native code.sentry-javascript/packages/core/src/utils-hoist/url.ts
Line 17 in 3d63621
Instead of just blanket replacing
parseUrl
, we'll slowly convert all it's usages to using a new helper, which looks something like so:@sentry/core
, and implementparseStringToURL
sentry-javascript/packages/browser-utils/src/instrument/xhr.ts
Line 150 in 3d63621
sentry-javascript/packages/browser/src/integrations/breadcrumbs.ts
Line 36 in 3d63621
sentry-javascript/packages/opentelemetry/src/utils/parseSpanDescription.ts
Line 23 in 3d63621
sentry-javascript/packages/node/src/integrations/http/SentryHttpInstrumentation.ts
Line 17 in 3d63621
sentry-javascript/packages/node/src/integrations/node-fetch/SentryNodeFetchInstrumentation.ts
Line 6 in 3d63621
sentry-javascript/packages/browser/src/tracing/request.ts
Line 22 in 3d63621
sentry-javascript/packages/browser-utils/src/metrics/browserMetrics.ts
Line 9 in 3d63621
With that, we can also refactor
getSanitizedUrlString
, which should provide some performance benefits.sentry-javascript/packages/core/src/utils-hoist/url.ts
Line 55 in 3d63621
sentry-javascript/packages/bun/src/integrations/bunserver.ts
Line 10 in 3d63621
sentry-javascript/packages/opentelemetry/src/utils/getRequestSpanData.ts
Line 9 in 3d63621
sentry-javascript/packages/node/src/integrations/node-fetch/SentryNodeFetchInstrumentation.ts
Line 6 in 3d63621
sentry-javascript/packages/node/src/integrations/http/SentryHttpInstrumentation.ts
Line 14 in 3d63621
sentry-javascript/packages/opentelemetry/src/utils/parseSpanDescription.ts
Line 22 in 3d63621
Reminder list:
extractQueryParamsFromUrl
?The text was updated successfully, but these errors were encountered: