Sorry that you're still having trouble viewing data. I wanted to bring up another potential solution that was brought to my attention that should help with what you were trying to accomplish with yarn debug. It is possible to run the node process with inspector in the same sense to assist with debugging.
We use the following command in our package.json
file to run our app in dev mode:"start:web": "ts-node-dev src/server.ts",
You could try updating this start command to: ts-node-dev --inspect -- my-script.ts
This should allow you to accomplish the same thing as yarn debugging, as yarn is essentially just invoking this same command behind the scenes. More information can be found in the nodejs documentation
As for the api memory issues you've been having with your data, it may be due to you utilizing the app with a dataset that is too large for the default performance configuration. In your api's .env
file, there should be a variable called GROUP_BY
that has a default value of grouping by day
. This can be set to either month, quarter,
to help optimize grouping for larger data. You can find a deeper dive into these settings within our documentation for performance configurations
If you're still having trouble after messing with those configurations, then it could be that your organization is a larger cloud customer than we have anticipated. In that case, our team would love to work with you as we're always looking for opportunities to support and continuously scale our app for larger cloud customers. Let us know if any of that helps and whether that's something you'd be interested in!