TypeScript import errors
PS C:\Users\Developer\Documents\restro-ms-backend> npm run build
> tsc
src/endpoints/[Link]:15 - error TS2305: Module '"../types"' has no exported member
'AppContext'.
3 import { type AppContext, Task } from "../types";
~~~~~~~~~~
src/endpoints/[Link]:27 - error TS2305: Module '"../types"' has no exported member
'Task'.
3 import { type AppContext, Task } from "../types";
~~~~
src/endpoints/[Link]:15 - error TS2305: Module '"../types"' has no exported member
'AppContext'.
3 import { type AppContext, Task } from "../types";
~~~~~~~~~~
src/endpoints/[Link]:27 - error TS2305: Module '"../types"' has no exported member
'Task'.
3 import { type AppContext, Task } from "../types";
~~~~
src/endpoints/[Link]:15 - error TS2305: Module '"../types"' has no exported member
'AppContext'.
3 import { type AppContext, Task } from "../types";
~~~~~~~~~~
src/endpoints/[Link]:27 - error TS2305: Module '"../types"' has no exported member
'Task'.
3 import { type AppContext, Task } from "../types";
~~~~
src/endpoints/[Link]:15 - error TS2305: Module '"../types"' has no exported member
'AppContext'.
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 1/6
3 import { type AppContext, Task } from "../types";
~~~~~~~~~~
src/endpoints/[Link]:27 - error TS2305: Module '"../types"' has no exported member 'Task'.
3 import { type AppContext, Task } from "../types";
~~~~
src/routes/twilio-endpoints/twilioWebhook [Link]:10 - error TS2305: Module '"../../deepgram"'
has no exported member 'fetchMenu'.
5 import { fetchMenu, findCustomer, callData } from "../../deepgram";
~~~~~~~~~
src/routes/twilio-endpoints/twilioWebhook [Link]:21 - error TS2305: Module '"../../deepgram"'
has no exported member 'findCustomer'.
5 import { fetchMenu, findCustomer, callData } from "../../deepgram";
~~~~~~~~~~~~
src/routes/twilio-endpoints/twilioWebhook [Link]:35 - error TS2305: Module '"../../deepgram"'
has no exported member 'callData'.
5 import { fetchMenu, findCustomer, callData } from "../../deepgram";
~~~~~~~~
Found 11 errors in 5 files.
Errors Files
2 src/endpoints/[Link]
2 src/endpoints/[Link]
2 src/endpoints/[Link]
2 src/endpoints/[Link]
3 src/routes/twilio-endpoints/twilioWebhook [Link]
PS C:\Users\Developer\Documents\restro-ms-backend>
These TypeScript build errors mean that your imports are pointing to symbols that don’t actually exist
in the files you’re importing from.
Here’s what’s going on for each case:
1. ../types is missing AppContext and Task
Your imports look like this:
ts
import { type AppContext, Task } from "../types";
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 2/6
But in src/[Link] (or wherever ../types points), there is no export for AppContext or Task.
Fix options:
If these types should exist, define and export them in src/[Link]:
ts
// src/[Link]
export type AppContext = {
env: any;
ctx: any;
};
export interface Task {
id: string;
title: string;
completed: boolean;
}
If you don’t need them anymore, remove them from the import:
ts
// If only Task is needed, or none
import type { AppContext } from "../types"; // or remove entirely
2. ../../deepgram is missing fetchMenu, findCustomer, and callData
Your code says:
ts
import { fetchMenu, findCustomer, callData } from "../../deepgram";
But in src/[Link] (or wherever ../../deepgram points), none of those functions are exported.
Fix options:
If they exist but aren’t exported, add them:
ts
// src/[Link]
export function fetchMenu() { /* ... */ }
export function findCustomer() { /* ... */ }
export const callData = {};
If they don’t exist anymore, remove or replace the imports with the correct functions you have
now.
3. Why this happened
This typically happens when:
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 3/6
You renamed or deleted a type/function but didn’t update imports.
You copied code from another project but didn’t bring over its type/function definitions.
File paths or exports were changed during refactor.
4. How to quickly detect missing exports
Run:
bash
grep -R "export" src/[Link]
grep -R "export" src/[Link]
This will list everything actually exported, so you can cross-check.
If you want, I can go through your src/[Link] and src/[Link] and give you the exact missing
exports to add so the build passes without breaking functionality.
Do you want me to do that?
{
"compilerOptions": {
/* Base Options: */
"esModuleInterop": true,
"skipLibCheck": true,
"target": "es2022",
"verbatimModuleSyntax": false,
"allowJs": true,
"resolveJsonModule": true,
"moduleDetection": "force",
/* Strictness */
"noImplicitAny": false,
"noImplicitThis": true,
"strictNullChecks": true,
"strict": true,
"noUncheckedIndexedAccess": true,
/* [Link] Configuration (updated from Cloudflare Workers) */
"moduleResolution": "node",
"module": "commonjs",
"outDir": "./dist",
"rootDir": "./src",
"noEmit": false,
"lib": ["es2022"],
"types": [
"@types/node"
]
},
"exclude": ["node_modules", "dist", "tests"],
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 4/6
"include": ["src/**/*"]
}
whats the issue in here?
Your [Link] isn’t what’s causing those TS2305 errors — the errors are purely about missing
exports in your source files, not compiler settings.
That said, I do notice a couple of things in your config that could cause confusion or unexpected
behavior:
1. allowJs: true + rootDir: "./src"
If you have .js files outside src/, they will be ignored during compilation.
If you have .js files inside src/, they’ll be compiled — but TypeScript won’t check them strictly
unless you also have checkJs: true.
Impact: Not directly related to your error, but if you think TypeScript should be type-checking .js files, it
currently won’t.
2. module: "commonjs" with ES2022 target
You’re mixing an ES2022 target with CommonJS module output.
That’s fine if you’re running in Node (CJS mode), but it might cause issues if other parts of the code
use import/export and rely on ESM behavior.
3. verbatimModuleSyntax: false
This setting affects whether TypeScript strips unused imports.
It’s fine here, but if you were expecting type-only imports to remain untouched, you might want to
set this to true.
4. No paths / alias config
If you’re importing like ../types and moving files around, having a paths alias (e.g., @types/*) helps
prevent breakage.
Bottom line for your build errors
Your config is fine for compilation.
The real problem is that:
src/[Link] doesn’t export AppContext or Task.
src/[Link] doesn’t export fetchMenu, findCustomer, or callData.
Once you either add those exports or remove the broken imports, your build will succeed without
touching [Link].
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 5/6
If you want, I can patch your src/[Link] and src/[Link] with safe placeholder exports so your
build passes immediately, and you can fill them in later.
That would let you get to a clean build without guessing missing type definitions.
Do you want me to do that?
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 6/6
