You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Perhaps worth pointing out that the current Opentelemetry package versions used by next-contentlayer conflict with the optional peer dependency versions from latest next:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: next@13.2.4
npm ERR! Found: @opentelemetry/api@1.1.0
npm ERR! node_modules/@opentelemetry/api
npm ERR! @opentelemetry/api@"~1.1.0" from @contentlayer/utils@0.3.1
npm ERR! node_modules/@contentlayer/utils
npm ERR! @contentlayer/utils@"0.3.1" from @contentlayer/cli@0.3.1
npm ERR! node_modules/@contentlayer/cli
npm ERR! @contentlayer/cli@"0.3.1" from contentlayer@0.3.1
npm ERR! node_modules/contentlayer
npm ERR! contentlayer@"0.3.1" from the root project
npm ERR! @contentlayer/utils@"0.3.1" from @contentlayer/core@0.3.1
npm ERR! node_modules/@contentlayer/core
npm ERR! @contentlayer/core@"0.3.1" from @contentlayer/cli@0.3.1
npm ERR! node_modules/@contentlayer/cli
npm ERR! @contentlayer/cli@"0.3.1" from contentlayer@0.3.1
npm ERR! node_modules/contentlayer
npm ERR! 5 more (@contentlayer/client, @contentlayer/source-files, ...)
npm ERR! 4 more (@contentlayer/source-files, ...)
npm ERR! peer @opentelemetry/api@"^1.1.0" from @effect-ts/otel@0.14.1
npm ERR! node_modules/@effect-ts/otel
npm ERR! @effect-ts/otel@"^0.14.0" from @contentlayer/utils@0.3.1
npm ERR! node_modules/@contentlayer/utils
npm ERR! @contentlayer/utils@"0.3.1" from @contentlayer/cli@0.3.1
npm ERR! node_modules/@contentlayer/cli
npm ERR! @contentlayer/cli@"0.3.1" from contentlayer@0.3.1
npm ERR! node_modules/contentlayer
npm ERR! 5 more (@contentlayer/core, @contentlayer/source-files, ...)
npm ERR! @effect-ts/otel@"^0.14.1" from @effect-ts/otel-exporter-trace-otlp-grpc@0.14.1
npm ERR! node_modules/@effect-ts/otel-exporter-trace-otlp-grpc
npm ERR! @effect-ts/otel-exporter-trace-otlp-grpc@"^0.14.0" from @contentlayer/utils@0.3.1
npm ERR! node_modules/@contentlayer/utils
npm ERR! @contentlayer/utils@"0.3.1" from @contentlayer/cli@0.3.1
npm ERR! node_modules/@contentlayer/cli
npm ERR! 5 more (@contentlayer/core, @contentlayer/source-files, ...)
npm ERR! 1 more (@effect-ts/otel-sdk-trace-node)
npm ERR! 15 more (@effect-ts/otel-exporter-trace-otlp-grpc, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @opentelemetry/api@"^1.4.0" from next@13.2.4
npm ERR! node_modules/next
npm ERR! peer next@"^12 || ^13" from next-contentlayer@0.3.1
npm ERR! node_modules/next-contentlayer
npm ERR! next-contentlayer@"0.3.1" from the root project
npm ERR! next@"13.2.4" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @opentelemetry/api@1.4.1
npm ERR! node_modules/@opentelemetry/api
npm ERR! peerOptional @opentelemetry/api@"^1.4.0" from next@13.2.4
npm ERR! node_modules/next
npm ERR! peer next@"^12 || ^13" from next-contentlayer@0.3.1
npm ERR! node_modules/next-contentlayer
npm ERR! next-contentlayer@"0.3.1" from the root project
npm ERR! next@"13.2.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
Activity
stale commentedon Mar 27, 2023
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
schickling commentedon Mar 27, 2023
Sorry about the inconvenience. I'll upgrade the underlying packages soon!
MR-Addict commentedon Mar 27, 2023
Thanks for your commitment to upgrading the underlying packages.
jasongerbes commentedon Mar 28, 2023
Perhaps worth pointing out that the current Opentelemetry package versions used by
next-contentlayerconflict with the optional peer dependency versions from latestnext:schickling commentedon May 31, 2023
This should be addressed with the
0.3.3release. 🎉