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

bootprint-openapi has peerDependency to old bootprint #5

Closed
creinig opened this issue Jan 8, 2020 · 2 comments
Closed

bootprint-openapi has peerDependency to old bootprint #5

creinig opened this issue Jan 8, 2020 · 2 comments

Comments

@creinig
Copy link

creinig commented Jan 8, 2020

When installing bootprint-openapi via npm install -g bootprint bootprint-openapi I get the following error:

npm WARN bootprint-openapi@4.0.2 requires a peer of bootprint@^2.0.1 but none was installed.

Installing with npm install -g bootprint@2.0.1 bootprint-openapi in turn results in

npm WARN bootprint-json-schema@4.0.2 requires a peer of bootprint@^4.0.1 but none was installed.
npm WARN bootprint-base@4.0.2 requires a peer of bootprint@^4.0.1 but none was installed.

I assume the peerDependency from bootprint-openapi@4.0.2 to bootprint@2.0.1 is a typo and should instead read bootprint@4.0.1 (since it has been updated just 10 days ago)?

@nknapp
Copy link
Member

nknapp commented Jan 8, 2020

That's right. It should be 4.0.1

Actually, if it had a devDependency to bootprint, the peerDependency would be updated as well. I'll fix that

@nknapp nknapp closed this as completed Jan 8, 2020
@nknapp nknapp reopened this Jan 8, 2020
@nknapp nknapp closed this as completed in 91120f3 Jan 8, 2020
@nknapp
Copy link
Member

nknapp commented Jan 8, 2020

should be solved with 4.0.3
peerDependencies of local package are now set to the current version on version bumps and publish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants