VITE0017Keep Vite server.fs.strict enabled

Why it happens

Vite configuration runs in both dev and build pipelines. Narrow, explicit settings reduce surprises across SSR, workers, and local file access.

Fix

Remove disabled fs strict, or move it to the Vite runtime/API that owns that behavior.

Example

Keep fs strict enabled

Before

export default defineConfig({
  server: {
    fs: { strict: false },
  },
})

After

export default defineConfig({
  server: {
    fs: { strict: true },
  },
})

Verify the fix

Run only this rule after editing so the report stays focused on the diagnostic you are closing:

pnpm vite-doctor . --framework vite --rules vite/server/no-disabled-fs-strict

Useful links

• Upstream docs

Related rule

• vite/server/no-disabled-fs-strict