ReferenceError: process is not defined

[REX500]

Cannot use sdk's get method on Vite @^3.0.8 as it defaults to process.env.EDGE_CONFIG.
Instead it should accept a parameter for edge config, OR support Vite bundler.

Code example:

import { get } from '@vercel/edge-config';

export const config = { matcher: '/welcome' };

export function middleware(): Promise<any> {
	try {
		return get('greeting').then((res: any) => res.json());
	} catch (error) {
		console.log(error);
		return Promise.resolve(false);
	}
}

Error when trying to call middleware function:

ReferenceError: process is not defined

I'm guessing it happens when we try to read EDGE_CONFIG var key in the init function in index.edge.ts file:

// lazy init fn so the default edge config does not throw in case
// process.env.EDGE_CONFIG is not defined and its methods are never used.
function init(): void {
  // eslint-disable-next-line @typescript-eslint/no-unnecessary-condition
  if (!defaultEdgeConfigClient) {
    defaultEdgeConfigClient = createClient(process.env.EDGE_CONFIG);
  }
}

How to reproduce:

• create a new project with Vite
• install vercel's edge config sdk
• paste the middleware code I posted above
• call it
• see the error

Proposed fix for the init function:
Update the init function:

// lazy init fn so the default edge config does not throw in case
// process.env.EDGE_CONFIG is not defined and its methods are never used.
function init(edgeConfig: string): void {
  // eslint-disable-next-line @typescript-eslint/no-unnecessary-condition
  if (!defaultEdgeConfigClient) {
    defaultEdgeConfigClient = createClient(edgeConfig);
  }
}

Update the get function and so on.... Ill gladly make a PR with the fix if you guys think it makes sense.

[dferber90]

That's a tricky one!

We'd still like to fall back to process.env.EDGE_CONFIG and have it as the default. This is what enables people to do

import {get} from @vercel/edge-config

instead of

import {createClient} from @vercel/edge-config
createClient().get()

How does vite usually deal with accessing the env from a package? Is there maybe anything we could do on that side?

[tcc-sejohnson]

@REX500

The solution for Vite is to construct the client using your connection string:

import { createClient } from '@vercel/edge-config';
const client = createClient(/* your connection string */);
// client now has access to `get` and the other methods

[tcc-sejohnson]

Closing this one as there's no bug here, but I did create a PR to better-document the setup process for Vite: #117