[v8] Changes to serverless package

[AbhiPrasad]

[v8] Changes to serverless package

[Lms24]

yeah that's fine. I was just under the impression that there's no direct replacement for the default init from @sentry/serverless but that's probably fine. Also remembered that we tell folks to use the Node SDK in the Azure functions guide anyway.

[AbhiPrasad]

On that note, are we sure that serverless environments work with Otel? I guess as long as we're in a Node-compatible runtime they should work but not sure how well we investigated this yet.

With CJS they should work pretty fine! But we need to investigate esm (also the serverless packages use monkeypatching require right now, that will break).

I'm gonna move forward with Option 2 - splitting the package up! Created a tasklist to reflect the work.

[mydea]

generally sounds good to me - should we still have a (generic?) serverless package? is there anything that could be in there? What about non-aws/gcp serverless environments, could they/would they so far have used the serverless package?

[Lms24]

Agreed, sounds like a good change! Should the AWS/GCP packages inherit from @sentry/serverless which in turn continues to be based on @sentry/node?

On that note, are we sure that serverless environments work with Otel? I guess as long as we're in a Node-compatible runtime they should work but not sure how well we investigated this yet.

[lforst]

@mydea @Lms24 I don't particularly see the value behind a generic @sentry/serverless package. What would be in there? So far any other serverless envs would have just used the Node pkg.

I think purely splitting it up into provider-specific packages is the way to go. Let's kill @sentry/serverless.

[mydea]

If we don't have any "generic" serverless code (that could not also just live in core) then yes, let's delete it!