Matt Savoia

@KathrynCrawford Dealing with the same issue, have you found any solution or workaround?

I'm having what looks like the same exact issue and switching node from v18.4.0 back to node v16.14.2 seems to have done the trick.