Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RangeError: Maximum call stack size exceeded

See original GitHub issue

Describe the bug RangeError: Maximum call stack size exceeded when a recursion is present in the spec

To Reproduce Steps to reproduce the behavior:

Given a yml file that references itself
run redocly preview-docs
the error

    at tn (https://cdn.redoc.ly/redoc/latest/bundles/redoc.standalone.js:8:647081)
    at new Nc (https://cdn.redoc.ly/redoc/latest/bundles/redoc.standalone.js:39:68016)
    at https://cdn.redoc.ly/redoc/latest/bundles/redoc.standalone.js:39:65200
    at Array.map (<anonymous>)
    at Pc (https://cdn.redoc.ly/r```

**Expected behavior**
The docs are rendered properly

**Logs**
```RangeError: Maximum call stack size exceeded
    at tn (https://cdn.redoc.ly/redoc/latest/bundles/redoc.standalone.js:8:647081)
    at new Nc (https://cdn.redoc.ly/redoc/latest/bundles/redoc.standalone.js:39:68016)
    at https://cdn.redoc.ly/redoc/latest/bundles/redoc.standalone.js:39:65200
    at Array.map (<anonymous>)
    at Pc (https://cdn.redoc.ly/r```

**OpenAPI definition**
"openapi": "3.0.0",

**Redocly Version(s)**
1.0.0-beta.105

**`Node.js` Version(s)**
18.2.0

Issue Analytics

State:
Created a year ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

felipelohacommented, Aug 24, 2022

@tatomyr I didnt know if we had to update the cli. we tried it out and everything is working. thanks

0reactions

tatomyrcommented, Aug 19, 2022

Hi @felipeloha,

Redocly CLI uses the latest version of Redoc. The reason it doesn’t get fixed for you might be some caching. Could you check this in the incognito mode?