-
Notifications
You must be signed in to change notification settings - Fork 224
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
Explicitly install peerdependencies #1233
Conversation
FYI this seems to have been breaking debian as well. You should update your commit message to match. My guess is that it's a Node v8 -> v10 and associated npm upgrade breakage, but I didn't test that. Applying this patch manually has resolved the issue, tested on both |
Wow, I'd say that's still a problem on
|
90210bf
to
f628299
Compare
CouchDB Docker images now use nodejs 10 by default. This commit updates Travis to use nodejs 10 when running integration tests. It also adds and `npm ls` check which will fail if there are unmet peer dependencies in package.json.
Builds against recent nodejs versions are failing due to missing peerdependencies. This adds the following packages explicitly in package.json: * acorn * ajv Fixes #1230 (properly)
We can now reference this directly from npm instead of resolving from GitHub. The reference to GitHub was incorrect (referenced non-existent gh-pages tag) which resulted in a resolution error in the latest npm.
f628299
to
58be287
Compare
The build now checks that there are no missing peer dependencies. I still don't understand why the webpack step fails in the CouchDB CI Dockerfiles but not in Travis or on a local machine but checking for missing peer dependencies at least prevents this specific problem. |
Overview
Builds on CentoOS are failing due to missing peerdependencies.
This adds the following packages explicitly in package.json:
Testing recommendations
I verified the fix with the following Dockerfile:
GitHub issue number
Fixes #1230 (properly)
Related Pull Requests
Checklist