Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upRangeError: Maximum call stack size exceeded #933
Comments
This comment has been minimized.
This comment has been minimized.
tunnckoCore
commented
Jul 16, 2017
|
Same here. @feross, more precise stack
|
This comment has been minimized.
This comment has been minimized.
tunnckoCore
commented
Jul 16, 2017
|
Just found that problem comes from |
This comment has been minimized.
This comment has been minimized.
tunnckoCore
commented
Jul 16, 2017
•
|
Yep. Seems like lazy-cache made that problem. Probably @animsaj, so if you use some kind of caching mechanism try to remove it and run Standard again. That was my problem. |
This comment has been minimized.
This comment has been minimized.
luispabon
commented
Jul 18, 2017
|
I don't have lazy-cache on my project though. |
This comment has been minimized.
This comment has been minimized.
tunnckoCore
commented
Jul 18, 2017
•
|
Yea, probably, but probably the problem is some sort like this, any source may help ;] But yea, definitely seems like bug on their side. |
This comment has been minimized.
This comment has been minimized.
luispabon
commented
Jul 18, 2017
|
No source, this happens without a single file to lint. |
This comment has been minimized.
This comment has been minimized.
tunnckoCore
commented
Jul 18, 2017
•
|
Duh.. ;d Clean cache and reinstall? If you use npm@5+ try The whole thing is pretty weird. First issue ( #882 ) is published on May 11, last Standard version on April 14, and the plugin on March 28. No changes, no new versions, plus that it is |
This comment has been minimized.
This comment has been minimized.
luispabon
commented
Jul 18, 2017
•
|
Edit: will post all my comments to #882 which is older and of which this issue is a duplicate of. |
This comment has been minimized.
This comment has been minimized.
|
Will close as duplicate of #882 |
animsaj commentedJun 25, 2017