-
Notifications
You must be signed in to change notification settings - Fork 31
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
isOlderThan
is not a function
#533
Comments
I've been trying to wrap my head around this and cannot seem to be able to. If I debug locally (I get the same error) and inspecting the
I'm not sure where Let's go ahead and assume this is something I am doing wrong. Where would I even start? |
Just for tracking purposes, the Additionally, the |
Can you try setting |
Hey @jd-carroll - this is most likely fixed by getsentry/sentry-javascript#12160 which we're gonna release today. |
@Lms24 awesome, thank you, I'll look for that in a bit! @lforst I tried setting that but it still seems to be throwing the same error (but maybe less...?) Additionally, I just noticed this in the error output:
I didn't think the Sentry bundler is actually changing the entry point for the lambda. If so, this is hugely concerning because none of my lambdas use "default" as the named entry point for AWS. Can either of you help me understand what is happening there? |
As a side note, I just patched my local code and everything seems to be working. I also inspected the output and confirmed that my named exports still exist. The output contains the following: // lambdas/user-account-details-handler/user-account-details-handler.ts?sentryProxyModule=true
var user_account_details_handler_default = void 0;
export {
user_account_details_handler_default as default,
handler
};
//# sourceMappingURL=lambda.mjs.map Nothing is ever assigned to |
@Lms24 It does not appear this was fixed in @sentry/core@8.3.0 (fyi) |
Yup, sorry about that, we had to close the PR in favor of a better fix |
Environment
Actual Result
Still investigating, but my builds are all failing with:
The text was updated successfully, but these errors were encountered: