fix(oas-extensions): moving oas
from being a peer to a hard dep
#819
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧰 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 thatfile:
reference when publishing a release. This was causing issues withinoas-extensions
where becauseoas
was listed as a peer dependency when I loaded in the latest release ofoas-extensions
it was trying to loadoas
from the samefile:
path in another repository of mine.Yikes!