fix(elysia): Set SDK metadata on the options passed to init

[Shubham-Padkonde]

init() copied userOptions into options and then applied SDK metadata to userOptions. When metadata was initially absent, the copied options passed to the underlying SDK did not receive Elysia's SDK name.

Apply SDK metadata to the options passed to the underlying SDK. The regression test uses the real metadata helper and checks that initNode receives sentry.javascript.elysia metadata.

Closes #24045

Original contribution generated with Claude Code; review follow-up prepared with OpenAI Codex assistance.

[github-actions]

👋 @mydea, @s1gr1d — Please review this PR when you get a chance!

[logaretm]

Thanks for the PR, it looks good mostly but I think we need to test this properly. I've called out a simple change in the existing test.

We should also assert the SDK metadata in both e2e test Elysia apps we have, each should detect the runtime/name correctly.

You can add an assertions in these test cases:

• sentry-javascript/dev-packages/e2e-tests/test-applications/elysia-bun/tests/errors.test.ts

  Line 21 in d0b4cca

  expect(errorEvent.transaction).toEqual('GET /test-exception/:id');

• sentry-javascript/dev-packages/e2e-tests/test-applications/elysia-node/tests/errors.test.ts

  Line 21 in d0b4cca

  expect(errorEvent.transaction).toEqual('GET /test-exception/:id');

Something like this should be fine:

expect(errorEvent.sdk?.name).toBe('sentry.javascript.elysia');

That checks the real event on both runtimes.

[logaretm]

We avoid asserting via mock.calls[0]?.[0], and I don't think it asserts what we want to test.

Could we drop the applySdkMetadata mock and assert what initNode should receive.

expect(mockInitNode).toHaveBeenCalledWith(
  expect.objectContaining({
    _metadata: { sdk: expect.objectContaining({ name: 'sentry.javascript.elysia' }) },
  }),
);

[Shubham-Padkonde]

Removed the applySdkMetadata mock and now assert the actual Elysia metadata received by initNode, as requested. Confirmed that the revised test fails when metadata is applied to userOptions instead of options, and all 31 Elysia package tests pass with the fix. Formatting and lint checks pass on the changed unit test.

Also added the requested errorEvent.sdk?.name assertion to both the Node and Bun E2E error tests. Their formatting checks pass. Local E2E execution stopped before running tests because this checkout has no packed SDK tarballs; those two runtime checks still need CI verification. I did not run the full monorepo suite. Prepared with OpenAI Codex assistance.

[logaretm]

Tests are failing due to a mockApplySdkMetadata not being defined, probably a simple typo

[Shubham-Padkonde]

The failure came from the new Bun-runtime test added on develop: the automatic CI merge retained its reference to the removed mock. Merged develop and changed that assertion to verify the runtime and actual Elysia SDK metadata received by initNode (7fe29ad).

All 32 Elysia package tests now pass locally, including the Bun-runtime case; the changed test passes formatting and lint. The E2E Hydrogen failures in the previous run are separate from this missing-reference failure and are not claimed fixed by this change. Prepared with Codex assistance.