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

@primer/css canary releases don't satisfy peer dependency #32

Closed
shawnbot opened this issue Jun 20, 2019 · 0 comments · Fixed by #33
Closed

@primer/css canary releases don't satisfy peer dependency #32

shawnbot opened this issue Jun 20, 2019 · 0 comments · Fixed by #33
Assignees
Labels

Comments

@shawnbot
Copy link
Contributor

We currently have @primer/css listed as a peer dependency with the >=12 version specifier, which causes npm to bail when this package is installed alongside canary releases, which are always 0.0.0-{sha}. The version specifier is too specific because the first release of @primer/css (as opposed to primer) was 12.0.0, so this can be loosened to *.

@shawnbot shawnbot added the bug label Jun 20, 2019
@shawnbot shawnbot self-assigned this Jun 20, 2019
@shawnbot shawnbot mentioned this issue Jun 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant