vite: Type 'DevEnvironment' is not assignable to type 'Environment'. #16488

kuchta · 2025-02-13T06:37:10Z

Simplest possible vite configuratin has TS error:

vite.config.ts:

export default defineConfig({
	base: process.env.BASE_URL ?? '/',
	build: {
		sourcemap: true,
	},
	plugins: [
		tailwindcss(),
	]
}

Vite now uses PluginOption instead of Plugin, so maybe the plugin needs some update.

No overload matches this call.
  The last overload gave the following error.
    Type 'Plugin<any>[]' is not assignable to type 'PluginOption'.
      Type 'Plugin<any>[]' is not assignable to type 'PluginOption[]'.
        Type 'Plugin<any>' is not assignable to type 'PluginOption'.
          Type 'import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]_1/node_modules/vite/dist/node/index").Plugin<any>' is not assignable to type 'import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]/node_modules/vite/dist/node/index").Plugin<any>'.
            Types of property 'hotUpdate' are incompatible.
              Type 'import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]/node_modules/rollup/dist/rollup").ObjectHook<(this: HotUpdatePluginContext, options: import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]_1/node_modules/vite/dist/node/index").HotUpdateOptions) => void | ... 1 more ... | Pr...' is not assignable to type 'import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]/node_modules/rollup/dist/rollup").ObjectHook<(this: HotUpdatePluginContext, options: import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]/node_modules/vite/dist/node/index").HotUpdateOptions) => void | ... 1 more ... | Prom...'.
                Type '(this: HotUpdatePluginContext, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<void | EnvironmentModuleNode[]>' is not assignable to type 'ObjectHook<(this: HotUpdatePluginContext, options: HotUpdateOptions) => void | EnvironmentModuleNode[] | Promise<void | EnvironmentModuleNode[]>> | undefined'.
                  Type '(this: HotUpdatePluginContext, options: import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]_1/node_modules/vite/dist/node/index").HotUpdateOptions) => void | ... 1 more ... | Promise<...>' is not assignable to type '(this: HotUpdatePluginContext, options: import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]/node_modules/vite/dist/node/index").HotUpdateOptions) => void | ... 1 more ... | Promise<...>'.
                    The 'this' types of each signature are incompatible.
                      Type 'HotUpdatePluginContext' is not assignable to type 'HotUpdatePluginContext'. Two different types with this name exist, but they are unrelated.
                        The types of 'environment.pluginContainer.environment' are incompatible between these types.
                          Type 'import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]/node_modules/vite/dist/node/index").Environment' is not assignable to type 'import("/Users/kuchta/Projects/radixverse/node_modules/.deno/[email protected]_1/node_modules/vite/dist/node/index").Environment'.
                            Type 'DevEnvironment' is not assignable to type 'Environment'.

The text was updated successfully, but these errors were encountered:

philipp-spiess · 2025-02-13T10:54:26Z

@kuchta Hey! I created a frewsh Vite 6.1.0 setup and added our plugin with the latest version and can not reproduce this issue. Can you please attach a repro for this?

kuchta · 2025-02-13T12:14:03Z

@philipp-spiess Hi Philipp, it seems like it's doing in projects initialized by deno.

$ deno -A npm:create-vite
✔ Project name: … vite-project
✔ Select a framework: › React
✔ Select a variant: › TypeScript

Scaffolding project in /Users/kuchta/Projects/vite-project...

Done. Now run:

  cd vite-project
  deno install
  deno run dev

$ cd vite-project

$ deno i

$ deno add npm:tailwindcss npm:@tailwindcss/vite
Add npm:[email protected]
Add npm:@tailwindcss/[email protected]

$ deno check vite.config.ts 
Check file:///Users/kuchta/Projects/vite-project/vite.config.ts
TS2769 [ERROR]: No overload matches this call.
  The last overload gave the following error.
    Type 'Plugin<any>[]' is not assignable to type 'PluginOption'.
      Type 'Plugin<any>[]' is not assignable to type 'PluginOption[]'.
        Type 'Plugin<any>' is not assignable to type 'PluginOption'.
...

corentinclichy · 2025-02-13T20:02:11Z

I have the same issue on on Adonis application (with inertia)

Avaray · 2025-02-17T05:24:53Z

Same in Astro.

Updating is not solving this issue in Astro.

kuchta · 2025-02-17T08:28:04Z

Seems like create-vite is not installing latest versions:

  "dependencies": {
    "react": "^18.3.1",
    "react-dom": "^18.3.1"
  },
  "devDependencies": {
    "@eslint/js": "^9.11.1",
    "@types/react": "^18.3.10",
    "@types/react-dom": "^18.3.0",
    "@vitejs/plugin-react": "^4.3.2",
    "eslint": "^9.11.1",
    "eslint-plugin-react-hooks": "^5.1.0-rc.0",
    "eslint-plugin-react-refresh": "^0.4.12",
    "globals": "^15.9.0",
    "typescript": "^5.5.3",
    "typescript-eslint": "^8.7.0",
    "vite": "^5.4.8"
  }

After updating to latest versions it's OK

$ deno outdated -u --latest
Updated 5 dependencies:
 - npm:@types/react     18.3.18 -> 19.0.9
 - npm:@types/react-dom  18.3.5 -> 19.0.3
 - npm:react             18.3.1 -> 19.0.0
 - npm:react-dom         18.3.1 -> 19.0.0
 - npm:vite              5.4.14 ->  6.1.0

$ deno check vite.config.ts 
Check file:///Users/kuchta/Projects/vite-project/vite.config.ts

kuchta · 2025-02-17T14:57:04Z

FYI, deno doesn't run latest versions unless specifically instructed to do so by --reload param denoland/deno#28148

knd775 · 2025-02-28T22:26:02Z

This is happening to us in a fully up to date sveltekit project using vite 6.2.0 and tailwind 4.0.9. We're using node (v22.12.0)

nalejandroveron · 2025-03-03T19:34:38Z

Same when using in a fresh Tanstack Start project, setting the plugin in app.config.ts

IanVS · 2025-03-04T19:53:10Z

I am also struggling with this. It's obviously a mismatch between versions, but I'm not entirely sure versions of what. I'm writing a vite plugin, and I've made sure that the version of vite and rollup are the same in the plugin and the project using it, but still getting this TS error. I've noticed that when I use import type {Plugin} from 'rollup' it works fine, but not when importing from vite. Even though both vite are 6.2...

Edit: sorry, I thought this was the vite repo. My experience is probably not relavant here.

But I would suggest that anyone having trouble with the tailwind plugin even after updating everything to latest, try removing node_modules and your lockfile, and re-installing. I have a feeling there's a transitive dep issue.

Robin-Hoodie · 2025-03-15T22:42:15Z

But I would suggest that anyone having trouble with the tailwind plugin even after updating everything to latest, try removing node_modules and your lockfile, and re-installing. I have a feeling there's a transitive dep issue.

Tried this - didn't work unfortunately
Installed the latest [email protected] version.
Why is this issue closed?

ShaunLWM · 2025-03-22T22:39:15Z

Just started a project with Vite and had the same issue

  "dependencies": {
    "@tailwindcss/vite": "^4.0.15",
    "@workspace/ui": "workspace:*",
    "lucide-react": "^0.483.0",
    "react": "^19.0.0",
    "react-dom": "^19.0.0",
    "tailwindcss": "^4.0.15"
  },
  "devDependencies": {
    "@types/node": "^22.13.11",
    "@types/react": "^19.0.12",
    "@types/react-dom": "^19.0.4",
    "@vitejs/plugin-react": "^4.3.4",
    "globals": "^15.15.0",
    "react-scan": "^0.3.3",
    "typescript": "~5.7.3",
    "vite": "^6.2.2"
  }

Used npx npkill, deleted all node_modules in my monorepo, pnpm i again, restart ts-server and lint error is gone.

teddythinh · 2025-04-02T08:57:52Z

After upgrading Vite, closing and reopening the code editor works for me. I use VS Code.

monarchwadia · 2025-05-10T04:37:02Z

I had pnpm workspaces enabled. I had installed the package in the parent project instead of the actual subfolder.

Oops.

philipp-spiess added the needs reproduction label Feb 13, 2025

kuchta closed this as completed Feb 17, 2025

kuchta mentioned this issue Feb 17, 2025

Bump generated dependencies versions in create-vite initializer vitejs/vite#19446

Closed

4 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

vite: Type 'DevEnvironment' is not assignable to type 'Environment'. #16488

vite: Type 'DevEnvironment' is not assignable to type 'Environment'. #16488

kuchta commented Feb 13, 2025 •

edited

Loading

philipp-spiess commented Feb 13, 2025

kuchta commented Feb 13, 2025 •

edited

Loading

corentinclichy commented Feb 13, 2025

Avaray commented Feb 17, 2025 •

edited

Loading

kuchta commented Feb 17, 2025

kuchta commented Feb 17, 2025

knd775 commented Feb 28, 2025 •

edited

Loading

nalejandroveron commented Mar 3, 2025

IanVS commented Mar 4, 2025 •

edited

Loading

Robin-Hoodie commented Mar 15, 2025 •

edited

Loading

ShaunLWM commented Mar 22, 2025

teddythinh commented Apr 2, 2025

monarchwadia commented May 10, 2025

vite: Type 'DevEnvironment' is not assignable to type 'Environment'. #16488

vite: Type 'DevEnvironment' is not assignable to type 'Environment'. #16488

Comments

kuchta commented Feb 13, 2025 • edited Loading

philipp-spiess commented Feb 13, 2025

kuchta commented Feb 13, 2025 • edited Loading

corentinclichy commented Feb 13, 2025

Avaray commented Feb 17, 2025 • edited Loading

kuchta commented Feb 17, 2025

kuchta commented Feb 17, 2025

knd775 commented Feb 28, 2025 • edited Loading

nalejandroveron commented Mar 3, 2025

IanVS commented Mar 4, 2025 • edited Loading

Robin-Hoodie commented Mar 15, 2025 • edited Loading

ShaunLWM commented Mar 22, 2025

teddythinh commented Apr 2, 2025

monarchwadia commented May 10, 2025

kuchta commented Feb 13, 2025 •

edited

Loading

kuchta commented Feb 13, 2025 •

edited

Loading

Avaray commented Feb 17, 2025 •

edited

Loading

knd775 commented Feb 28, 2025 •

edited

Loading

IanVS commented Mar 4, 2025 •

edited

Loading

Robin-Hoodie commented Mar 15, 2025 •

edited

Loading