Typescript - Unable to export `Agent#lambda(...)` from client library due to absence of exported inline AwsLambda.Context.

Is your feature request related to a problem? It’s currently not possible to export a function form a typescript module when calling Agent#lambda because the interface AwsLambda#Context (defined in-line) is not exported in index.d.ts.

// Typescript file: some-app.ts
import apm = require('elastic-apm-node');
const apmInstance = apm.start();

export const run = apmInstance.lambda({} as any); // ERROR: Exported variable 'run' has or is using name 'AwsLambda.Context' from external module [...]

Describe the solution you’d like AwsLambda could potentially be exported (?). Might be tricky since we currently export a default agent with export =.

Describe alternatives you’ve considered

1. Currently hacking by adding as any when exporting function from typescript file.

export const run = apmInstance.lambda({} as any) as any;

1. Directly exporting AwsLambda but blocked by default export of Agent

[jpike88]

This is pain in the butt, just ran into this… how is it that this is the only library out of hundreds I’ve seen that decides to break TS in such a weird way? Why not just fix your declaration files so paying customers can use types without hassle?

Exported variable 'apm' has or is using name 'Agent' from external module "/server/node_modules/elastic-apm-node/index" but cannot be named.

Just bump the major version, and change how the exports from your declaration file are done, it’s worth it for such a critical issue as it renders your types useless outside an extremely simple use case.

[trusktr]

I’ve opened a request to fix issues like these in TypeScript by bringing declaration files to parity with language features. https://github.com/microsoft/TypeScript/issues/35822