Skip to content

Direct call to process.env in Abstract Client #349

Description

@mattkenefick

What is the current behavior?

Direct calls to the global process object looking for an API key in the AbstractClient

Steps to reproduce

Run it in an environment without process

Expected behavior

Gracefully ignore the process object if it does not exist.

Please tell us about your environment

I've included @deepgram/sdk into a TypeScript SDK that compiles out for web and node environments. When using the SDK in a web environment, the app throws an error because process.env doesn't exist; I'd imagine you'd run into that for import.meta environments as well, like Vite.

Other information

I added a polyfill for it in my sdk for the time being.

(() => {
	const globalScope: any = typeof globalThis !== 'undefined' ? globalThis : typeof window !== 'undefined' ? window : {};

	if (!globalScope.process) {
		globalScope.process = {};
	}

	if (!globalScope.process.env) {
		globalScope.process.env = {};
	}
})();

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions