You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have a web application that generates a swagger-ui page for clients based on their apikey, but for some reason Docker is unable to successfully build versions 5.7.2 and 5.9.0. I get the following message:
I see that the swagger-api has a ramda dependency and I have various versions of ramda 0.29.x in my package-lock.json, but I don't understand why is this complaining about having a newer version? One workaround I found was to directly install ramda using npm, but that still installs version 0.29.x, adds extra lines to my package.json, and I want to minimize the amount of dependencies in my package.json
My webapp builds and runs perfectly fine locally, it's only when I use Docker to build my code that I get this message.
I deprecated my swagger version to 5.4.2 and the error message went away when I built the container in Docker
What cause this and will this be resolved in future swagger-ui versions?
I can provide more of my package.json and package-lock.json if requested but certain parts must be redacted
Thanks
The text was updated successfully, but these errors were encountered:
The ramda dep comes from ApiDOM that swagger-ui uses under the hood. From the information you provided I cannot tell you what is wrong as it's problem specific to your project.
I've just issued this PR swagger-api/apidom#3384 that updates ramda to v0.29.1 for ApiDOM (before 0.29.0 was used).
I can only speculate that during your install the npm re-conciliates the dependencies and only installs [email protected] and fails to install [email protected] (needed by other dependencies in your project). 0.29.x and 0.28.x are backward incompatible versions of ramda.
Sorry that all I've got from the information in the description of this issue.
Q&A
Content & configuration
package.json dependencies:
Screenshots
How can we help?
Hi, I have a web application that generates a swagger-ui page for clients based on their apikey, but for some reason Docker is unable to successfully build versions 5.7.2 and 5.9.0. I get the following message:
npm ERR! Invalid: lock file's [email protected] does not satisfy [email protected]
npm ERR! Missing: [email protected] from lock file
I see that the swagger-api has a ramda dependency and I have various versions of ramda 0.29.x in my package-lock.json, but I don't understand why is this complaining about having a newer version? One workaround I found was to directly install ramda using npm, but that still installs version 0.29.x, adds extra lines to my package.json, and I want to minimize the amount of dependencies in my package.json
My webapp builds and runs perfectly fine locally, it's only when I use Docker to build my code that I get this message.
I deprecated my swagger version to 5.4.2 and the error message went away when I built the container in Docker
What cause this and will this be resolved in future swagger-ui versions?
I can provide more of my package.json and package-lock.json if requested but certain parts must be redacted
Thanks
The text was updated successfully, but these errors were encountered: