question-mark
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.

Maximum call stack Exceeded

See original GitHub issue

Hey guys,

I have a very large project that I am trying to use with this plugin and I am constantly getting the following error whenever I try to use it.

RangeError: Maximum call stack size exceeded at D:\dev\editor\node_modules\gulp-inline-ng2-template\node_modules\async\dist\async.js:842:20 at D:\dev\editor\node_modules\gulp-inline-ng2-template\node_modules\async\dist\async.js:5218:17 at D:\dev\editor\node_modules\gulp-inline-ng2-template\node_modules\async\dist\async.js:339:31 at D:\dev\editor\node_modules\gulp-inline-ng2-template\parser.js:114:13

Based on the discussion here I have changed your code locally to use:

process.nextTick(cb);

and everything seems to be working as expected. I can not seem to reproduce the problem on a smaller project. Just wanted to make you aware of the issue and maybe you can investigate further.

Thanks,

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:2
  • Comments:14 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
ludohenincommented, Jul 18, 2016

published as 2.0.5

1reaction
josh-fishercommented, Jun 24, 2016

My problem is identical to what @fcastill describes. Can either use the PR that I submitted or filter out any files that do not have components. Maybe a better solution would be to have some code that ignores any files that do not have components from the start.

Read more comments on GitHub >

github_iconTop Results From Across the Web

javascript - Maximum call stack size exceeded error
It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you...
Read more >
JavaScript Error: Maximum Call Stack Size Exceeded
If you see the “Maximum Call Stack Size Exceeded” error, there's likely a problem with a recursive function within your JavaScript code.
Read more >
Uncaught RangeError: Maximum call ... - Net-Informations.Com
Maximum call stack size exceeded error. This error is almost always means you have a problem with recursion in JavaScript code, as there...
Read more >
RangeError: Maximum call stack size exceeded - Educative.io
The most common source for this error is infinite recursion. You must have a recursive function in your code whose base case is...
Read more >
RangeError: Maximum call stack size exceeded in JavaScript
The "RangeError: Maximum call stack size exceeded" error occurs when a function is called so many times that the invocations exceed the call...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found