Version Packages (mailing 1.2.0, mailing-core 1.1.2)

Consumes the pending changesets: mailing 1.1.0->1.2.0 (minor), mailing-core 1.1.1->1.1.2 (patch). CHANGELOGs updated.

Author: psugihara

.changeset/fix-mjml2html-async-type-drift.md

@@ -1,5 +1,24 @@
 # mailing
 
+## 1.2.0
+
+### Minor Changes
+
+- aae797d: Update peer dependency ranges to the last two major versions of the frameworks mailing supports: `next@^15 || ^16` and `react`/`react-dom@^18 || ^19` (previously `next@^12–14`, `react@^17–18`). This removes peer-dependency warnings for projects on current Next.js and React, which the e2e matrix now exercises.
+
+### Patch Changes
+
+- 71141c7: Make the generated `.mailing` preview build resilient to upstream toolchain drift.
+
+  - The render helpers (`mailing-core` and `mailing`) now assert the awaited (unwrapped) return type of `mjml2html`. `@types/mjml` pulls `@types/mjml-core` via a `*` range, which now resolves to v5 where `mjml2html` is typed as async (`Promise<MJMLParseResults>`); since mailing pins `mjml@^4` (synchronous at runtime), the mismatched types broke `next build` type-checking. The assertion is a no-op when the resolved types are already synchronous.
+  - `next build` of the `.mailing` app type-checks any imported `node_modules` `.ts` source, so third-party packages that ship broken or too-modern TypeScript (e.g. `iron-session`'s raw `next/index.ts`, or a newer `@types/node` than the resolved compiler can parse) failed the build. Type errors are now ignored for end users during that build (kept on for mailing's own dev via `MM_DEV`), mirroring the existing `eslint.ignoreDuringBuilds`.
+  - `export-previews` failed with `SyntaxError: Unexpected token '<'` in projects whose tsconfig sets `jsx: "preserve"` (e.g. Next.js and Remix scaffolds): esbuild-register passed that through and left JSX untranspiled when loading email templates. The require hook now overrides `tsconfigRaw` to force the automatic JSX runtime.
+  - Loading previews failed with `ReferenceError: require is not defined` in ESM projects (`"type": "module"`, e.g. Remix's JavaScript template): esbuild-register's CommonJS require-hook rewrote `.js` files to `require(...)`, which throws once Node executes them as ESM. In ESM projects the hook now only handles `.ts`/`.tsx`/`.jsx` and leaves `.js` to Node.
+  - The `.mailing` preview app failed under Next 16, which defaults both `next build` and the dev server to Turbopack — its analysis can't follow the app's dynamic requires (the generated Prisma client during build; `uglify-js` at runtime, returning 500s). On Next >= 15 the build now passes `--webpack` and the programmatic dev server passes `webpack: true` (older Next uses webpack by default).
+
+- Updated dependencies [71141c7]
+  - mailing-core@1.1.2
+
 ## 1.1.0
 
 ### Minor Changes

.changeset/next-react-peer-range.md

@@ -1,6 +1,6 @@
 {
   "name": "mailing",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "main": "dist/mailing.cjs.js",
   "license": "MIT",
   "homepage": "https://github.com/sofn-xyz/mailing#readme",
@@ -77,7 +77,7 @@
     "html-minifier-terser": "^7.0.0",
     "iron-session": "^6.2.1",
     "lodash": "^4.17.21",
-    "mailing-core": "^1.1.0",
+    "mailing-core": "^1.1.2",
     "mjml": "^4.12.0",
     "node-fetch": "^2.6.7",
     "node-html-parser": "^6.1.1",

packages/cli/CHANGELOG.md

@@ -1,5 +1,17 @@
 # mailing-core
 
+## 1.1.2
+
+### Patch Changes
+
+- 71141c7: Make the generated `.mailing` preview build resilient to upstream toolchain drift.
+
+  - The render helpers (`mailing-core` and `mailing`) now assert the awaited (unwrapped) return type of `mjml2html`. `@types/mjml` pulls `@types/mjml-core` via a `*` range, which now resolves to v5 where `mjml2html` is typed as async (`Promise<MJMLParseResults>`); since mailing pins `mjml@^4` (synchronous at runtime), the mismatched types broke `next build` type-checking. The assertion is a no-op when the resolved types are already synchronous.
+  - `next build` of the `.mailing` app type-checks any imported `node_modules` `.ts` source, so third-party packages that ship broken or too-modern TypeScript (e.g. `iron-session`'s raw `next/index.ts`, or a newer `@types/node` than the resolved compiler can parse) failed the build. Type errors are now ignored for end users during that build (kept on for mailing's own dev via `MM_DEV`), mirroring the existing `eslint.ignoreDuringBuilds`.
+  - `export-previews` failed with `SyntaxError: Unexpected token '<'` in projects whose tsconfig sets `jsx: "preserve"` (e.g. Next.js and Remix scaffolds): esbuild-register passed that through and left JSX untranspiled when loading email templates. The require hook now overrides `tsconfigRaw` to force the automatic JSX runtime.
+  - Loading previews failed with `ReferenceError: require is not defined` in ESM projects (`"type": "module"`, e.g. Remix's JavaScript template): esbuild-register's CommonJS require-hook rewrote `.js` files to `require(...)`, which throws once Node executes them as ESM. In ESM projects the hook now only handles `.ts`/`.tsx`/`.jsx` and leaves `.js` to Node.
+  - The `.mailing` preview app failed under Next 16, which defaults both `next build` and the dev server to Turbopack — its analysis can't follow the app's dynamic requires (the generated Prisma client during build; `uglify-js` at runtime, returning 500s). On Next >= 15 the build now passes `--webpack` and the programmatic dev server passes `webpack: true` (older Next uses webpack by default).
+
 ## 1.1.1
 
 ### Patch Changes

packages/cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mailing-core",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "main": "dist/mailing-core.cjs.js",
   "license": "MIT",
   "description": "Fun email development environment (core library only)",