rollup-plugin-node-externals might be compatible with just enforce: 'pre'.

See vitejs/vite#6198

Add rollup-plugin-sourcemaps

I would like to make https://github.com/wasm-tool/rollup-plugin-rust compatible with vite, any hints of what I should do in order to accomplish that?

Thanks in advance

The eslint example didn't work out of the box because any typescript related eslint configs are applied after source transform.

Esbuild transpiles .ts files to plain javascript, then eslint runs on its output. If eslint config has rules for typescript it complains about missing return types and whatnot. The giveaway is the line numbers are incorrect, and the errors in the IDE don't match those thrown on vite build.

Found the fix here: https://github.com/ehutch79/vite-eslint#warning

Adding the enforce setting fixes the issue. The eslint worked as expected in serve and build modes:

{
      ...eslint({
        include: "./src/**/*.(vue|js|jsx|ts|tsx)",
      }),
      enforce: "pre",

      // uncomment this to lint only on `vite build`
      // apply: "build",
    },

As a side note,

in your examples you use file patterns like this: '**/*.+(vue|js|jsx|ts|tsx)'. I think this allows to match file..ts ? Is there a specific reason to allow "one or more dots" before the file extension?

I think the descriptions of the Statuses are a bit ambiguous.
I get that "Covered" mean it's in the core functionality of Vite. But "shipped out of the box with Vite" means the same to me.
Does it means "Included" are maintained by Vite team, available in @Vite npm namespace ?
Have a nice day

Hi

Great site! 👍

I tried to use the Rollup strip plugin, which is listed as "compatible".

I copied the config shown when clicking the little info icon:

// ...
import strip from "@rollup/plugin-strip"

export default defineConfig({
  // other options here...
  
  plugins: [
    vue(),
    WindiCSS(),
    {
      ...strip(),
      apply: 'build',
    },
  ]
}

Somehow couldn't get it to work. Specifically: console.log() and console.assert() still showed after vite build.

Curiously no warnings or any errors from vite build, so the config appears to be syntactically correct at least.

I trried via rollupOptions as well but no luck:

  build: {
    rollupOptions: {
       plugins: [strip()],
    },

Instead I remembered an option in Terser, and I was able to strip console statements this way :

export default defineConfig({
  build: {
    terserOptions: {
      compress: {
        drop_console: true,
      },
    },
  },

Just wondering if the config for strip() is incorrect or there is something else it needs somehow?

Is it planned to make this list/a new list for Vite 3 plugins - personally I am specifically after a list of what plugins are already included in Vite 3