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

bower component raven-js results in downstream problem with yarn #27

Open
md8n opened this issue Jun 8, 2018 · 0 comments
Open

bower component raven-js results in downstream problem with yarn #27

md8n opened this issue Jun 8, 2018 · 0 comments

Comments

@md8n
Copy link

md8n commented Jun 8, 2018

If raven-js was installed with bower then the resulting entry in packages.json dependencies ends up as:

"@bower_components/raven-js": "getsentry/raven-js#3.26.1",

Or whichever version of raven-js of course.

However, raven-js has it's own packages.json that does NOT specify a version member. As a result yarn borks on it and dies.

In this case - packages.json of a package does not have a version member - it may require that the package is included in another way e.g. a direct call to yarn add

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

1 participant