feat(oxfmt): publish preset types and .js export

Add oxfmt-preset.d.ts and a types condition on the ./oxfmt export so TypeScript resolves without consumer shims. Rename the preset from .mjs to .js under this package's type module.

Made-with: Cursor

Author: kentcdodds

README.md

@@ -62,9 +62,9 @@ configure anything more than the defaults).
 Install [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html) alongside this
 package (it is listed in `peerDependencies`).
 
-The `@epic-web/config/oxfmt` entry resolves to a plain `.mjs` preset so Node
-does not need to strip TypeScript from files under `node_modules` when you
-extend it.
+The `@epic-web/config/oxfmt` entry resolves to a plain `.js` preset (this
+package uses `"type": "module"`) so Node does not need to strip TypeScript from
+files under `node_modules` when you extend it.
 
 Create an `oxfmt.config.ts` file in your project root:
 
@@ -108,7 +108,7 @@ Epic projects. Adjust in your `defineConfig` if your layout differs.
   <summary>Customizing Oxfmt</summary>
 
 If you want to customize things heavily, you can copy the options from
-[`oxfmt-preset.mjs`](./oxfmt-preset.mjs) into your own config. For small tweaks,
+[`oxfmt-preset.js`](./oxfmt-preset.js) into your own config. For small tweaks,
 keep spreading `epicOxfmt` and override or extend fields as in the example
 above.
 

docs/decisions/011-oxfmt-over-prettier.md

@@ -26,7 +26,7 @@ ignore files; lockfiles and generated paths were duplicated across
 
 Adopt **Oxfmt** as the shared formatter for `@epic-web/config`:
 
-- Replace the Prettier entry point with a published `oxfmt-preset.mjs` (via
+- Replace the Prettier entry point with a published `oxfmt-preset.js` (via
   `defineConfig`) and document `oxfmt` as a peer dependency.
 - Map the old Prettier options into Oxfmt where supported; document gaps (for
   example `insertPragma` / `requirePragma`, and regex-based Tailwind attribute
@@ -53,7 +53,7 @@ Adopt **Oxfmt** as the shared formatter for `@epic-web/config`:
 - Output is “Prettier-like” but not identical everywhere; teams should expect a
   one-time format churn when switching.
 - Some Prettier options and comment forms have no equivalent; those are called
-  out in `oxfmt-preset.mjs` and the readme.
+  out in `oxfmt-preset.js` and the readme.
 
 Historical decision docs that mention Prettier remain valid as context for
 _formatting style_; this decision supersedes the _tool choice_ for applying that

oxfmt-preset.d.ts

@@ -0,0 +1,4 @@
+import { type OxfmtConfig } from 'oxfmt'
+
+declare const preset: OxfmtConfig
+export default preset

oxfmt-preset.mjs oxfmt-preset.jsoxfmt-preset.mjs renamed to oxfmt-preset.js

@@ -1,8 +1,9 @@
 import { defineConfig } from 'oxfmt'
 
 /**
- * Shared Oxfmt preset for `@epic-web/config` consumers (plain `.mjs` so Node does
- * not load TypeScript from `node_modules`).
+ * Shared Oxfmt preset for `@epic-web/config` consumers (plain `.js` under this
+ * package’s `"type": "module"` so Node does not execute TypeScript from
+ * `node_modules`).
  *
  * @see https://oxc.rs/docs/guide/usage/formatter/migrate-from-prettier.html
  */

oxfmt.config.mjs

@@ -1 +1 @@
-export { default } from './oxfmt-preset.mjs'
+export { default } from './oxfmt-preset.js'

package.json

@@ -13,7 +13,11 @@
   },
   "exports": {
     ".": "./index.js",
-    "./oxfmt": "./oxfmt-preset.mjs",
+    "./oxfmt": {
+      "types": "./oxfmt-preset.d.ts",
+      "import": "./oxfmt-preset.js",
+      "default": "./oxfmt-preset.js"
+    },
     "./typescript": "./typescript.json",
     "./reset.d.ts": "./reset.d.ts",
     "./oxlint": "./oxlint-config.json"

tsconfig.json

@@ -1,4 +1,4 @@
 {
 	"extends": "./typescript.json",
-	"include": ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]
+	"include": ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx", "oxfmt-preset.d.ts"]
 }