Registry / database / lambdaorm-client-node

lambdaorm-client-node

JSON →
library0.7.47jsnpmunverified

HTTP client for consuming Lambda ORM service (lambdaorm-svc). Current version 0.7.47. Enables querying remote ORM endpoints using lambda expressions (typed) or string expressions. Ships TypeScript definitions. Key differentiator: allows client-side lambda-like query syntax that compiles to SQL on the server. Useful for building Node.js applications that need a centralized data access layer via HTTP.

npm install lambdaorm-client-node
INSTALL
IMPORT
SIG · LAMBDAORM-CLIENT-N
L
lambdaorm-client-node
databasejavascriptv0.7.47
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

orm
import { orm } from 'lambdaorm-client-node'
import orm from 'lambdaorm-client-node'
Named export, not default export.
Orm
import { Orm } from 'lambdaorm-client-node'
Type for the orm instance, used for type annotations.
Plan
import type { Plan } from 'lambdaorm-client-node'
Type for query plan objects; use type import for TypeScript.

Initialize the ORM client, check connectivity with ping and health endpoints.

import { orm } from 'lambdaorm-client-node'; async function main() { try { orm.init('http://localhost:9291'); const pingResult = await orm.general.ping(); console.log(pingResult); const healthResult = await orm.general.health(); console.log(healthResult); } catch (error) { console.error(error); } } main();
Debug
Known issues
breakingVersion 0.x API is unstable. Breaking changes may occur between minor versions.
fix
Pin exact version or monitor release notes.
affects: >=0.0.0 <1.0.0
gotchaorm.init() must be called before any query or plan operation.
fix
Always call orm.init(baseUrl) at application startup.
affects: >=0.0.0
gotchaQuery results are plain objects, not model instances.
fix
Access properties directly; no ORM-specific methods available on results.
affects: >=0.0.0
gotchaType safety of lambda expressions depends on model type definitions. Using wrong model types leads to runtime errors.
fix
Ensure model files match server-side schema. Use code generation if available.
affects: >=0.0.0
Errors
Common errors & fixes
TypeError: orm.init is not a function
orm was not imported correctly (likely default import when named is required).
fix
Use named import: import { orm } from 'lambdaorm-client-node'
Error: Connection refused at http://localhost:9291
Lambda ORM service is not running or URL is incorrect.
fix
Start the lambdaorm-svc server and verify URL.
Property 'general' does not exist on type 'typeof import(...)'
orm.init() was not called or imports are incorrect.
fix
Ensure orm.init(baseUrl) is called before accessing orm.general.
Upgrade
Version history
0.7.47latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
4 hits · last 30 days
node
4
Resources
lambdaorm-client-node — npm install lambdaorm-client-node · libregistry