fix opentelemetry version incompatibility with next 13.2 - #407
Conversation
Sorry, something went wrong.
⚠️ No Changeset foundLatest commit: 1ffc717 Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset. Click here to learn what changesets are, and how to add one. Click here if you're a maintainer who wants to add a changeset to this PR 💥 An error occurred when fetching the changed packages and changesets in this PRSome errors occurred when validating the changesets config: The package or glob expression "examples-*" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch. |
Sorry, something went wrong.
This comment has been minimized.
- Workaround for contentlayerdev/contentlayer#386 - Next.js v13.2 and Contentlayer have an incompatibility because they depend on different versions of opentelemetry. - Fixed by specifying @opentelemetry/api in package.json, alternative to using npm install --force. - Redundant once contentlayerdev/contentlayer#407 is merged.
- Workaround for contentlayerdev/contentlayer#386 - Next.js v13.2 and Contentlayer have an incompatibility because they depend on different versions of opentelemetry. - Fixed by specifying @opentelemetry/api in package.json, alternative to using npm install --force. - Redundant once contentlayerdev/contentlayer#407 is merged.
|
This pull request 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. |
Sorry, something went wrong.
|
@schickling could you please take a look at this PR |
Sorry, something went wrong.
|
Thanks a lot for the PR! Looks like the tests are failing but I've implemented the same changes as part of #430. |
Sorry, something went wrong.
|
This should be addressed with the 0.3.2 release. 🎉 |
Sorry, something went wrong.
- Workaround for contentlayerdev/contentlayer#386 - Next.js v13.2 and Contentlayer have an incompatibility because they depend on different versions of opentelemetry. - Fixed by specifying @opentelemetry/api in package.json, alternative to using npm install --force. - Redundant once contentlayerdev/contentlayer#407 is merged.
fix #386
To reproduce the issue, you can do npm install next in @contentlayer/utils. It does not reproduce with yarn.