# Sls deploy - RangeError: Maximum call stack size exceeded

**URL:** <https://forum.serverless.com/t/sls-deploy-rangeerror-maximum-call-stack-size-exceeded/9298>\
**Category:** Serverless Framework\
**Created:** [September 11, 2019, 11:41am UTC](https://forum.serverless.com/t/sls-deploy-rangeerror-maximum-call-stack-size-exceeded/9298 "2019-09-11T11:41:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![GregH](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/gregh/32/3595_2.png) [@GregH](https://forum.serverless.com/u/GregH)\
**Post date:** [September 11, 2019, 11:41am UTC](https://forum.serverless.com/t/sls-deploy-rangeerror-maximum-call-stack-size-exceeded/9298/1 "2019-09-11T11:41:51Z")

</div>

Deploying with latest release (1.52) - today’s error is:  
`RangeError: Maximum call stack size exceeded at Function.[Symbol.hasInstance] (<anonymous>) at WriteStream (/builds/[yada]/node_modules/graceful-fs/graceful-fs.js:217:14)`

I think I’m going to have to update my deployment script to use the last stable version

---

<div class="post-metadata">

**Author:** ![GregH](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/gregh/32/3595_2.png) [@GregH](https://forum.serverless.com/u/GregH)\
**Post date:** [September 11, 2019, 11:47am UTC](https://forum.serverless.com/t/sls-deploy-rangeerror-maximum-call-stack-size-exceeded/9298/2 "2019-09-11T11:47:16Z")

</div>

Yup just changing the install serverless line in my CI script fixed it:

`- npm install -g serverless`

to:

`- npm install -g serverless@1.51`

---

<div class="post-metadata">

**Author:** ![warnerjonn](https://avatars.discourse-cdn.com/v4/letter/w/eb8c5e/32.png) [@warnerjonn](https://forum.serverless.com/u/warnerjonn)\
**Post date:** [March 3, 2021, 6:37am UTC](https://forum.serverless.com/t/sls-deploy-rangeerror-maximum-call-stack-size-exceeded/9298/3 "2021-03-03T06:37:30Z")

</div>

> [@GregH](#):
>
> RangeError: Maximum call stack size exceeded

This error is almost always means you have a problem with recursion in JavaScript code, as there isn’t any other way in JavaScript to consume lots of stack. Sometimes calling a recursive function over and over again, causes the browser to send you Maximum [call stack size exceeded](http://net-informations.com/js/err/range.htm) error message as the memory that can be allocated for your use is not unlimited.

How to fix it?

Wrap your recursive function call into a -

- setTimeout
- setImmediate
- process.nextTick

Also, you can localize the issue by setting a breakpoint on RangeError type of exception , and then adjust the code appropriately.