swagger-api / swagger-api/swagger-ui
Warning: Failed to parse source map
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A (please complete the following information)
- OS: macOS
- Browser: chrome
- Version: 114
- Method of installation: yarn
- Swagger-UI version: (swagger-ui-react: ^5.1.0)
- Swagger/OpenAPI version: OpenAPI 3.0
Screenshots
How can we help?
Hi! When running the swagger-ui-react (v5.1.0) with CRA react-scripts (v5.0) and react (v18), it shows a warning as we see in the image above. Looks like it's related to the libraries autolinker and remarkable. Is there an issue/PR addressing this problem?
Thank you for the amazing library! :)
Some other people are also facing this problem:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the swagger-ui-react package in a CRA application using react-scripts, then inspect how the autolinker and remarkable dependencies relate to the browser's source-map warning. Reproduce the warning with the reported versions and confirm that the warning no longer appears without breaking Swagger UI rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100