🐛 Bug Report: TablesDB is exported at runtime but missing from ESM typings (index.d.mts)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- node.js, typescript
- Domain
- api
Research direction
Start with the ESM typings entrypoint in dist/index.d.mts and compare its service exports with the runtime export and nearby entries such as Account, Databases, and Storage. Update the typings so the TablesDB import is available, then verify that TypeScript accepts import { TablesDB } from "node-appwrite".
Written by the indexing model from the issue text.
Description
👟 Reproduction steps
TablesDB is available at runtime from node-appwrite, but it is not exported in the ESM typings entrypoint (index.d.mts), which causes TypeScript import errors.
This leads to a mismatch between the runtime API and the type definitions.
👍 Expected behavior
TypeScript users should be able to import TablesDB the same way as other services:
import { TablesDB } from "node-appwrite";
Actual behavior
TypeScript reports that TablesDB is not exported:
Module '"node-appwrite"' has no exported member 'TablesDB'.
👎 Actual Behavior
Runtime export exists
In dist/index.js:
Object.defineProperty(exports, 'TablesDB', {
enumerable: true,
get: function () { return tablesDb.TablesDB; }
});
Typings export is missing
In dist/index.d.mts, TablesDB is not exported, while other services are:
export { Account } from './services/account.mjs';
export { Databases } from './services/databases.mjs';
export { Storage } from './services/storage.mjs';
// TablesDB missing
🎲 Appwrite version
Version 0.10.x
💻 Operating system
Windows
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
- Dominant language
- TypeScript
- Stars
- 257
- Forks
- 45
- Avg merge
- 11h 59m
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from appwrite/sdk-for-node
-
bug
appwrite/sdk-for-node#141 · 1 assignee ·
-
appwrite/sdk-for-node#136 · 3 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
appwrite/sdk-for-node#133 · 2 comments · 1 reaction ·
All issues in appwrite/sdk-for-node
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100