-
Notifications
You must be signed in to change notification settings - Fork 27.9k
Issues: vercel/next.js
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Error 403 "forbidden" when running 'next dev' through stunnel - Next.js ver. 15.2.2
CSS
Related to CSS.
Font (next/font)
Related to Next.js Font Optimization.
Instrumentation
Related to Next.js Instrumentation.
Runtime
Related to Node.js or Edge Runtime with Next.js.
#77045
opened Mar 12, 2025 by
designly1
Nextjs 15.1 not saving Static Content on Redis on build time using instrumentation using @neshca/cache-handler
Instrumentation
Related to Next.js Instrumentation.
#74958
opened Jan 16, 2025 by
joanaavelar
"use cache" with vercel otel - used Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Performance
Anything with regards to Next.js performance.
Math.random()
outside of "use cache"
bug
#72024
opened Oct 29, 2024 by
JamesRobertWiseman
Instrumentation in NextJS using custom library + altering RSC payload at Proxy layer
Instrumentation
Related to Next.js Instrumentation.
Output
Related to the the output configuration option.
#71601
opened Oct 22, 2024 by
sinwar
Server-side request forgery (SSRF)
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Output
Related to the the output configuration option.
#69903
opened Sep 10, 2024 by
monicavis
Code imported inside instrumentation.ts can't mutate imported modules
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Runtime
Related to Node.js or Edge Runtime with Next.js.
#69544
opened Sep 1, 2024 by
shkreios
Instrumentation files not included in standalone output
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
linear: next
Confirmed issue that is tracked by the Next.js team.
Output
Related to the the output configuration option.
#68740
opened Aug 9, 2024 by
moshie
Improper neutralization of HTTP headers for scripting syntax
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Output
Related to the the output configuration option.
#68435
opened Aug 2, 2024 by
monicavis
renderToString is not available in the Instrumentation hook
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
#67714
opened Jul 12, 2024 by
masiama
Opentelemetry - Spans for static resources and API pages not part of page load trace
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
#65989
opened May 20, 2024 by
bradleyberwick
Cannot compile /instrumentation whilst using babel since 14.2
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Module Resolution
Module resolution (CJS / ESM, module resolving).
Runtime
Related to Node.js or Edge Runtime with Next.js.
Webpack
Related to Webpack with Next.js.
#65324
opened May 3, 2024 by
Joezo
instrumentation.ts
cannot be used for instrumenting native modules with OpenTelemetry when native modules are imported from instrumentation.ts
bug
#64879
opened Apr 22, 2024 by
lforst
Multi-platform dependency cannot be correctly used with Next.js
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Output
Related to the the output configuration option.
Runtime
Related to Node.js or Edge Runtime with Next.js.
#64827
opened Apr 20, 2024 by
bripkens
Next.js Instrumentation can not import and resolve the node-bindings module.
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
#64471
opened Apr 14, 2024 by
PrinOrange
instrumentation.ts runtime showing as "edge" even when default runtime is supposed to be "nodejs" in local
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Runtime
Related to Node.js or Edge Runtime with Next.js.
#61728
opened Feb 6, 2024 by
juskek
instrumentation effect problem
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
#57880
opened Nov 1, 2023 by
justLuiz
1 task done
High-cardinality HTTP span names
Instrumentation
Related to Next.js Instrumentation.
#54694
opened Aug 29, 2023 by
BarryThePenguin
1 task done
Cannot set property message of ... which has only a getter
when an error happens during instrumentation hook being require'd
bug
#54417
opened Aug 23, 2023 by
SeriousBug
1 task done
OTel http instrumentation confuses NextTracerImpl
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
#51233
opened Jun 13, 2023 by
valkum
1 task done
OTel Span/Trace duplication when using a middleware
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
Runtime
Related to Node.js or Edge Runtime with Next.js.
#51231
opened Jun 13, 2023 by
valkum
1 task done
Instrumentation hook not resolved with mixed src dir and root instrumentation file
bug
Issue was opened via the bug report template.
Instrumentation
Related to Next.js Instrumentation.
#50420
opened May 27, 2023 by
lkostrowski
1 task done
ProTip!
Find all open issues with in progress development work with linked:pr.