Skip to content
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

Investigate and support Next.js instrumentation #171

Open
dario-piotrowicz opened this issue Dec 12, 2024 · 0 comments
Open

Investigate and support Next.js instrumentation #171

dario-piotrowicz opened this issue Dec 12, 2024 · 0 comments
Assignees

Comments

@dario-piotrowicz
Copy link
Contributor

dario-piotrowicz commented Dec 12, 2024

Next.js 15 introduced a loadInstrumentationModule methods that appears in our bundled worker which caused our workers to fail at runtime.

We're solved such issue by replacing the content of the loadInstrumentationModule methods with a no-op implementation (see: #169), this was the simplest and quickest way to work around the issue and unblock Next.js 15 for us, it is however most likely not the correct solution and almost certainly breaks Next.js' instrumentation.

So this issue is for investigating and understanding if and how we support instrumentation, and if we don't support it (which most likely we don't) find a way to do so.

@dario-piotrowicz dario-piotrowicz added enhancement New feature or request triage needs investigation and removed enhancement New feature or request triage labels Dec 12, 2024
@dario-piotrowicz dario-piotrowicz self-assigned this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant