List view
- No due date•11/12 issues closed
Issues that are about v8 instrumentation, usually related to OTEL or ESM (or both) https://github.com/getsentry/sentry-javascript/issues/12242
No due date•29/30 issues closedhttps://github.com/getsentry/sentry-javascript/issues/8724
No due date•2/2 issues closedhttps://github.com/getsentry/sentry-javascript/issues/8352
No due date•20/20 issues closedWe want to switch from domains to async local storage, this milestone tracks the work toward that: https://github.com/getsentry/sentry-javascript/issues/7691 Edit: Released with https://github.com/getsentry/sentry-javascript/releases/tag/7.48.0
No due date•14/14 issues closedhttps://github.com/getsentry/sentry-javascript/issues/6000
No due date•39/39 issues closedA milestone that tracks our efforts around supporting multiple JS runtimes: https://github.com/getsentry/sentry-javascript/issues/5611
No due date•12/12 issues closedThis issue tracks the support for Performance Issues in the JavaScript SDK https://github.com/getsentry/sentry/discussions/34968
No due date•5/5 issues closedDetails and the roadmap are here https://github.com/getsentry/sentry-javascript/issues/5492
No due date•13/13 issues closedDue to the growing high number of users upgrading which each latest JS SDK release, it demands that we protect those users with E2E tests. These tests should ensure that they are able to download and install the latest version of the Sentry SDK, while still being able to build and run their JS applications. Further, same as developers want to be on the latest version of our SDK they want to be on the latest version of the 3rd party libraries and frameworks they use to build their applications. When a new version of those major frameworks is release we should be prepared to support them in a timely manner and with confidence What do we want to do? E2E test definiton: tbc - download, install, build, run Base definition of E2E tests to be applied to following paltforms (frameworks & libraries): - react - react canary - nextjs - nextjs canar Goal: - Deliver with confidence with currently supported platforms - Support new releases of Major frameworks - Canary releases - enable SLOs
No due date•13/13 issues closed- Async stack traces - [Notion Async Functions](https://www.notion.so/sentry/23Q2-WEBFE-Async-Functions-5a5d819137b04eaca73b2e0191215c4f) - Transport mod detection - Stop using domains
No due date•3/3 issues closedThis Milestone tracks our progress toward a Sentry SDK for https://remix.run/
No due date•29/29 issues closedTracking work toward the v8 major release List of deprecated items that will be removed: https://github.com/getsentry/sentry-javascript/issues/5194
No due date•97/97 issues closedIn an effort to gather issues and feature requests related to the sentry SDK for NextJS and further anything specific around hosting on Vercel. This milestone will serve to prioritize what our users need most.
No due date•15/15 issues closedAdd support in the JS SDK for propagating Dynamic Sampling Context (DSC). [Refer SDK Developer Documentation](https://develop.sentry.dev/sdk/performance/dynamic-sampling-context/) for full details [Based originally on the propagation format for distributed context: Baggage](https://www.w3.org/TR/baggage/) Should be applied in way that allows compatibility with other Sentry SDKs, ensuring proper distributed tracing functionality and simplifying intercommunications, ingestion, and being a good citizen with other 3rd party implementations working with baggage, via consumption or adding to.
No due date•43/43 issues closedWork needed to set ourselves up for https://github.com/getsentry/sentry-javascript/milestone/7
No due date•62/62 issues closedThis milestone tracks issues and PRs related to getting our SDK more treeshakeable and our bundle size lowered. Release plan here: https://github.com/getsentry/sentry-javascript/issues/4240
No due date•71/71 issues closedWe want to collect issues related to enhancing release stability for the javascript SDK For example but not limited to integration tests
No due date•60/60 issues closedFor gathering open issues related to sentry working with NextJs 12 major release. Will prioritise ensuring that functionality working on NextJs 11 continue to work on 12, then consider new features of NextJs 12 (middleware for example).
No due date•5/5 issues closedTo gather more data from the internal workings of SDKs on client side, this initiative sets a way for gathering information to empower SDK maintainers and Sentry to make data driven decisions about how to enhance SDKs, products, and features.
No due date•7/7 issues closedTracking work toward our next major release v7
No due date•198/198 issues closed- No due date•8/8 issues closed
- No due date•2/2 issues closed
- No due date•1/1 issues closed
- No due date•7/7 issues closed
- No due date•3/3 issues closed
- No due date•7/7 issues closed