fix: pin swagger-ui-dist to v3.30.0 #5991
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The commit message should say |
raymondfeng
reviewed
Jul 22, 2020
| "version": "1.19.0", | ||
| "resolved": "https://registry.npmjs.org/@types/body-parser/-/body-parser-1.19.0.tgz", | ||
| "integrity": "sha512-W98JrE0j2K78swW4ukqMleo8R7h/pFETjM2DQ90MF6XK2i4LO4W3gQ71Lt4w3bfm2EvVSyWHplECvB5sK22yFQ==", | ||
| "@babel/code-frame": { |
There was a problem hiding this comment.
It seems that some @babel/ dependencies are added incorrectly. Please run node bin/rebuild-package-locks.js @loopback/rest-explorer to fix it.
dhmlau
changed the title
raymondfeng
approved these changes
Jul 22, 2020
jannyHou
approved these changes
Jul 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to swagger-api/swagger-ui#6249
When clicked on the /ping controller, there is only loading icon.
This fix is suggested by @raymondfeng to revert to use 3.30.0.
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm testpasses on your machinepackages/cliwere updatedexamples/*were updated👉 Check out how to submit a PR 👈