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

fix(oas-extensions): moving oas from being a peer to a hard dep #819

Merged
merged 1 commit into from
Oct 9, 2023

Conversation

erunion
Copy link
Member

@erunion erunion commented Oct 9, 2023

🧰 Changes

Something I didn't know is that with Lerna if you use the file:../<dirname> syntax for loading dependencies in a monorepo, but do that for a peer dependency, Lerna and NPM won't change that file: reference when publishing a release. This was causing issues within oas-extensions where because oas was listed as a peer dependency when I loaded in the latest release of oas-extensions it was trying to load oas from the same file: path in another repository of mine.

Yikes!

@erunion erunion added the bug Something isn't working label Oct 9, 2023
@erunion erunion marked this pull request as ready for review October 9, 2023 17:12
@@ -39,7 +39,7 @@
"prepack": "npm run build",
"test": "vitest run --coverage"
},
"peerDependencies": {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was originally a peer dep in https://github.com/readmeio/oas-extensions to save me the hassle of bumping it whenever I published a major release of oas but because they're all in the same repository now it makes sense to just have this listed as a regular dependency.

@erunion erunion merged commit 9372bd3 into main Oct 9, 2023
5 checks passed
@erunion erunion deleted the fix/oas-extensions branch October 9, 2023 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant