Vite plugin's global variables are `undefined` when using Deno

Anyone run across this before? Running Deno 2 and Vite 6beta.

I built a third-party Vite plugin, and now I'm testing it in a "native" Deno project (deno.json, not package.json, etc). However, all of the packages and dependencies are from npm. My Vite plugin defines a global like so.

...
return {
  define: {
    'XINK_VITE_MODE': JSON.stringify(mode)
  }
}
...

...
return {
  define: {
    'XINK_VITE_MODE': JSON.stringify(mode)
  }
}
...

In another part of my plugin package's code, not within the vite plugin definition itself, I grab the value during runtime, but it's logging undefinedundefined. This works fine when using Bun. I also tried doing globalThis.XINK_VITE_MODEglobalThis.XINK_VITE_MODE as well, since Vite's intellisense said it's supposed be available on windowwindow during devdev.

export const initRouter = async () => {
  const mode = XINK_VITE_MODE
  console.log('Vite mode is:', mode)
...
}

export const initRouter = async () => {
  const mode = XINK_VITE_MODE
  console.log('Vite mode is:', mode)
...
}

Deno•2y ago•

1 reply

Vite plugin's global variables are `undefined` when using Deno

...
return {
  define: {
    'XINK_VITE_MODE': JSON.stringify(mode)
  }
}
...

...
return {
  define: {
    'XINK_VITE_MODE': JSON.stringify(mode)
  }
}
...

export const initRouter = async () => {
  const mode = XINK_VITE_MODE
  console.log('Vite mode is:', mode)
...
}

export const initRouter = async () => {
  const mode = XINK_VITE_MODE
  console.log('Vite mode is:', mode)
...
}

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Deno

Chat about Deno, a modern runtime for JavaScript and TypeScript.

20,934 Members

Join

Vite plugin's global variables are `undefined` when using Deno

Vite plugin's global variables are `undefined` when using Deno

Continue the conversation

Deno

Continue the conversation

Deno

Similar Threads