Mastra•2mo ago

How to debug runtime server issues

Hi we are incorporating mastra into our codebase, but for certain tools calling our other existing functions we get errors like (From Typeorm and decimal.js imported in other files):

ColumnTypeUndefinedError: Column type for AppProfile#appName is not defined and cannot be guessed. Make sure you have turned on an "emitDecoratorMetadata": true option in tsconfig.json. Also make sure you have imported "reflect-metadata" on top of the main entry file in your application (before any entity imported).If you are using JavaScript instead of TypeScript you must explicitly provide a column type.
at ColumnTypeUndefinedError.TypeORMError [as constructor] (/Users/ericyu/Documents/GitHub/rutter-backend/node_modules/typeorm/error/TypeORMError.js:9:28)
at new ColumnTypeUndefinedError (/Users/ericyu/Documents/GitHub/rutter-backend/node_modules/typeorm/error/ColumnTypeUndefinedError.js:13:23)
at /Users/ericyu/Documents/GitHub/rutter-backend/node_modules/typeorm/decorator/columns/Column.js:45:23
at decorateClass$c (file:///Users/ericyu/Documents/GitHub/rutter-backend/.mastra/output/index.mjs:1097:24)
at file:///Users/ericyu/Documents/GitHub/rutter-backend/.mastra/output/index.mjs:1114:1
at ModuleJob.run (node:internal/modules/esm/module_job:271:25)
at async onImport.tracePromise.proto__ (node:internal/modules/esm/loader:578:26)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)

file:///Users/ericyu/Documents/GitHub/rutter-backend/.mastra/output/index.mjs:31
import Decimal, { Decimal as Decimal$1 } from 'decimal.js';
^^^^^^^
SyntaxError: The requested module 'decimal.js' does not provide an export named 'Decimal'
at ModuleJob._instantiate (node:internal/modules/esm/module_job:180:21)
at async ModuleJob.run ....

What is the best way to debug these?

Mastra Triager•11/15/25, 12:28 PM

Created GitHub issue: https://github.com/mastra-ai/mastra/issues/10135

GitHub

How to debug runtime server issues · Issue #10135 · mastra-ai/mastra

This issue was created from Discord post 1438928899571716206: Hi we are incorporating mastra into our codebase, but for certain tools calling our other existing functions we get errors like (From T...

Abhi Aiyer•11/18/25, 5:45 PM

Hi there @cyrieu could you give me some more information on your setup?

Abhi Aiyer•11/18/25, 5:45 PM

Is this happening when things are executing, or starting the server?

cyrieuOP•11/18/25, 7:16 PM

@Abhi Aiyer what is helpful to share? our dependencies are attached, and this is when we run mastra dev

message.txt6.52KB

Abhi Aiyer•11/18/25, 8:07 PM

Can you share your Mastra instantiation?

We should probably mark these modules as external so they dont get bundled. We'll be releasing https://github.com/mastra-ai/mastra/pull/10042 soon so you won't have to bundle through Mastra in the future.

GitHub

Server Adapters by NikAiyer · Pull Request #10042 · mastra-ai/mastra

Description

Related Issue(s)

Type of Change

Bug fix (non-breaking change that fixes an issue)
New feature (non-breaking change that adds functionality)
Breaking change (fix or feature that wo...

cyrieuOP•11/19/25, 10:07 PM

export const EnrichmentCoordinationAgent = new Agent({
name: "Enrichment Coordination Agent",
model: "openai/gpt-4o",
instructions: "Coordinate supplier enablement enrichment workloads.",
inputSchema: coordinationInputSchema,
outputSchema: coordinationOutputSchema,
maxRetries: 100,
promptCallback: buildPrompt,
tools: {
// data_fetch_config_guard: dataFetchConfigTool, // Confirm the item's data fetch configuration is compatible before dispatching work.
// job_dispatcher: dispatchTool, // Submit enrichment jobs while respecting dry-run guardrails.
// Notify stakeholders of progress and thread follow-up updates in Slack.
queue_inspector: queueInspectorTool, // Inspect the enrichment queue and surface the next work to tackle.
slack_update: slackUpdateTool,
log_locally: logLocallyTool,
},
});

export const mastra = new Mastra({
agents: {
EnrichmentCoordinationAgent,
},
observability: {
default: {
enabled: true,
},
configs: {
braintrust: {
serviceName: "rutter-backend",
exporters: [
new BraintrustExporter({
apiKey: process.env.BRAINTRUST_API_KEY,
}),
],
},
},
},
storage: new LibSQLStore({
url: "file:./mastra.db",
}),
});

cyrieuOP•11/19/25, 10:07 PM

i wanted to use mastra with our repo's existing logic, so excluding them from bundling would mean that i can't do that right?

Abhi Aiyer•11/19/25, 10:49 PM

Excluding them from bundling doesnt impact using the existing logic! The bundling mastra does is to make a server entrypoint that is optimized but we're realizing that since people have all kinds of JS code we should try and not be so clever with bundling.

Upcoming server adapters will help! Also we'll have a flag to mark everything "external" https://github.com/mastra-ai/mastra/pull/10218

Typically right now with bundling issues, you add externals of the dependencies that code may use to the Mastra class

GitHub

feat(deployer): Allow externals: true by LekoArts · Pull Request #...

Description
Add new bundler option:
const mastra = new Mastra({
bundler: {
externals: true
}
})
With this escape hatch, all dependencies (except workspace packages for now) will be treated ...

cyrieuOP•11/20/25, 3:51 AM

ok got it, so you would recommend adding various npm packages to to this externals array until the mastra dev command works? or i should just identify every npm module and add all of them to externals?

Abhi Aiyer•11/20/25, 7:50 AM

i would do the ones until it works. Because we do bundle modern modules well! Depends on your dependencies though!