Skip to content

Version 7.95.0 introduces breaking change due to type error #10310

Closed as not planned

Description

@VictrixHominum

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/serverless

SDK Version

7.95.0

Framework Version

No response

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

  1. Set @sentry/serverless version to 7.95.0
  2. Run ts-node-dev
  3. Try executing your lambda

Expected Result

Nothing, no reason why this should occur, its a type error from what I can tell. Reverting to 7.66.0 resolves the issue.

Actual Result

image

Activity

  1. moved this to Waiting for: Product Owner in GitHub Issues with 👀 2on Jan 24, 2024
  2. Lms24 commented on Jan 24, 2024

    @Lms24
    Member

    Hi @VictrixHominum thanks for writing in!

    Please make sure that all your installed @sentry/* packages are on exactly the same version.

    spanContext is a new function defined on the Span class and interface. It's exported from @sentry/core which is a dependency of @sentry/node and @sentry/serverless. I'm quite sure that @sentry/core or @sentry/types weren't updated correctly to 7.95.0 which would explain the issue.

    Please let us know if the issue still persists if all package versions align.

  3. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 2on Jan 24, 2024
  4. moved this to Waiting for: Community in GitHub Issues with 👀 2on Jan 24, 2024
  5. wereHamster commented on Jan 25, 2024

    @wereHamster

    Probably related: I also ran into a type error.

    https://unpkg.com/browse/@sentry/nextjs@7.95.0/

    • Package depends on "@sentry/node" version "7.95.0".
    • File types/server/httpIntegration.d.ts contains import("@sentry/node/build/types/integrations")
    • That version of "@sentry/node" does not include that file (no build folder in the package root).

    It looks like there is a spurious 'build/' folder in the import path that does not exist.

  6. moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 2on Jan 25, 2024
  7. Lms24 commented on Jan 25, 2024

    @Lms24
    Member

    Hmm I'm not sure how this is related but definitely looks like a bug. Not sure why TS would declare the type like this but I'll take a look how we can fix this. Thanks for investigating!

  8. 82 remaining items

  9. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 2on Mar 27, 2024
  10. johnsmith-gooddollar commented on Mar 28, 2024

    @johnsmith-gooddollar

    @lforst Thank you very much!

  11. moved this to Waiting for: Product Owner in GitHub Issues with 👀 2on Mar 28, 2024
  12. pedro3g commented on Mar 28, 2024

    @pedro3g

    I had the same problem with HCaptcha and thank you for helping me.

  13. moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 2on Mar 29, 2024
  14. Lms24 commented on Apr 17, 2024

    @Lms24
    Member

    Is anyone else still experiencing this issue? Please let us know. I'm gonna add the Waiting for: Community tag which will auto close the issue in a couple of weeks otherwise.

  15. moved this to Waiting for: Community in GitHub Issues with 👀 2on Apr 17, 2024
  16. getsantry commented on May 9, 2024

    @getsantry

    This issue has gone three weeks without activity. In another week, I will close it.

    But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


    "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

  17. ghost added on Aug 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions