Hi all. I'm not sure what's changed but I can't upgrade my stacks past 0.40.1. If I switch to anything higher (I've tried 0.40.2 -0.40.5) I get the following errors:

RangeError: Maximum call stack size exceeded
    at Object.normalize (path.js:265:12)
    at Object.join (path.js:429:18)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:43:33)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:48:12)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:48:12)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:48:12)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:48:12)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:48:12)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:48:12)
    at getManager (C:\Users\pa-de\Work\dentr\sst\node_modules\@serverless-stack\core\dist\packager\packager.js:48:12)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! dentr-sst@0.1.0 deploy: `sst deploy`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the dentr-sst@0.1.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\pa-de\AppData\Roaming\npm-cache\_logs\2021-08-31T10_40_48_799Z-debug.log

I'm running on Windows 10, if that makes a difference? I also have a stack that has an environment property check around if to determine whether to deploy it or not, like this:

if (!(skipStatic || isLocal)) {
  new AdminSite(app, `${stackIdPrefix}${AdminSite.STACK_SUFFIX}`);
}

Based on one of the bug fixes that went into 0.40.2, about handling empty stacks, I wonder if this could be the issue?

There's a PR with a fix for this

Ah, I forgot to look in Github and only searched in Slack... I'm way too used to finding the answers to things in here!