Changelog - 2026-10-16
dev-configs gains a browser tier
New FeatureIn one line. @venizia/dev-configs 0.3.1 adds presets for browser code that does not use React. The React preset now builds on them.
typescript
// .configs/oxlint.config.mts
import { defineConfig } from 'oxlint';
import { BrowserOxlintConfigs } from '@venizia/dev-configs/linters';
export default defineConfig(BrowserOxlintConfigs.create());What changed
BrowserOxlintConfigs.create()isoxlintConfigsplus thecrypto.randomUUIDban (the method isundefinedon a plain-http origin). Until now, only the React preset carried the ban.browserOxfmtConfigsisoxfmtConfigswitharrowParens: 'always'andbracketSameLine: true.tsconfig.browser.jsonandtsconfig.react.jsonare for a library that a bundler builds. They setmoduleResolution: bundler, add theDOMlib, and settypes: [], so no Bun types reachdist. The React config also setsjsx: react-jsx.ReactOxlintConfigsbuilds onBrowserOxlintConfigs. The rules are the same, and thecrypto.randomUUIDban now also covers.mjsand.cjsfiles.
| Tool | Backend | Browser | React |
|---|---|---|---|
| oxlint | oxlintConfigs | BrowserOxlintConfigs.create() | ReactOxlintConfigs.create() |
| oxfmt | oxfmtConfigs | browserOxfmtConfigs | browserOxfmtConfigs |
| ESLint | namingConventionConfigs | namingConventionConfigs | reactNamingConventionConfigs |
| tsconfig | tsconfig.common.json | tsconfig.browser.json | tsconfig.react.json |
Who is affected
- Backend projects. No action needed.
- A browser or React project that copies these overrides by hand. Switch to the new exports and delete the copies:
typescript
// Before
export default defineConfig({ ...oxfmtConfigs, arrowParens: 'always', bracketSameLine: true });
// After
export default defineConfig(browserOxfmtConfigs);