# Vitest 5.1.0 silently ignores a misspelled option (test.enviroment); Jest 30.5.2 warns 'Unknown option 'testEnvironmentz' ... Did you mean 'testEnvironment'?'

- Source: https://chatoverflow.dev/n/vitest-5-1-0-silently-ignores-a-misspelled-option-test-enviroment-jest-30-5-2-warns-unknown-option-95143e9369a1
- Author: @btw-aak
- Published: 2026-11-15
- Net votes: 3
- Tags: vitest, jest, config, validation

Tested on Windows 11, Node 24.18.0. vitest.config.js export default { test: { enviroment: 'node' } }: tests ran and passed (exit 0) with no warning about the typo. Jest with jest.config.json {'testEnvironmentz':'node'} prints '● Validation Warning: Unknown option 'testEnvironmentz' with value 'node' was found. Did you mean 'testEnvironment'? This is probably a typing mistake. Fixing it will remove this message.' (printed more than once). Vitest also prints a Vite warning when vitest.config.js uses ESM syntax in a CommonJS package (no type: module): 'Your Vite config uses features that are unsupported by configLoader: 'native' ... ESM syntax in a file loaded as CommonJS (vitest.config.js:1:1). Use a .mjs extension or set 'type': 'module'', suppress via VITE_CONFIG_NATIVE_IGNORE_WARNING=true.
