-
Notifications
You must be signed in to change notification settings - Fork 14
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
JavaScript heap out of memory #31
Comments
Thanks for your report. Would you be able to provide a schema reproducing the issue or a minimal version of the schema that reproduces the issue? This is not something that I can reproduce so far. |
Hi @HiDeoo thanks for your hard work on this. I am running into a similar issue. So any ideas would be awesome. Let me know if any other information would assist. We are using the same dependencies as in your example repo I think "dependencies": { We are trying with this schema:
|
I have tried the same config setup but with the It seems like the issue either lines in the |
I was running into the same issue, mine was due to having a circular reference in the component. |
Describe the bug
When trying to navigate to most of my generated swagger, it fails on the 3rd generated endpoint on the build.
This is both when trying to navigate to some pages on the working app, or by just running
npm run build
Below is the snippet of Swagger's OpenAPI 3.0.1 fo rthe last seen endpoint that I believe is what broke it, and the next endpoint.
To Reproduce
npm run build
Expected behavior
It should build and not freeze the webpage or terminal build
How often does this bug happen?
Every time
System Info
No response
Additional Context
This is for a dotnet 5 API using OpenApi 3.0.1 with Microsoft's built-in swagger support
The text was updated successfully, but these errors were encountered: