diff --git a/@ember/app-tsconfig/tsconfig.json b/@ember/app-tsconfig/tsconfig.json
index 2bdf087..edc04db 100644
--- a/@ember/app-tsconfig/tsconfig.json
+++ b/@ember/app-tsconfig/tsconfig.json
@@ -77,6 +77,13 @@
     // This does not require extensions, but allows them.
     "allowImportingTsExtensions": true,
 
+    // Allow importing JSON files directly. Node 24 strips TypeScript types
+    // and natively supports JSON module imports via `with { type: 'json' }`,
+    // which is now standard; TypeScript needs this flag to type-check those
+    // imports. Common uses include reading package.json inside build scripts
+    // and root-level config files.
+    "resolveJsonModule": true,
+
 
     // Don't implicitly pull in declarations from `@types` packages unless we
     // actually import from them AND the package in question doesn't bring its
diff --git a/@ember/library-tsconfig/tsconfig.json b/@ember/library-tsconfig/tsconfig.json
index 4af1546..a11337b 100644
--- a/@ember/library-tsconfig/tsconfig.json
+++ b/@ember/library-tsconfig/tsconfig.json
@@ -33,6 +33,13 @@
     // support importing `.ts` files.
     "allowImportingTsExtensions": true,
 
+    // Allow importing JSON files directly. Node 24 strips TypeScript types
+    // and natively supports JSON module imports via `with { type: 'json' }`,
+    // which is now standard; TypeScript needs this flag to type-check those
+    // imports. Common uses include reading package.json inside build scripts
+    // and root-level config files.
+    "resolveJsonModule": true,
+
     // Trying to check Ember apps and addons with `allowJs: true` is a recipe
     // for many unresolveable type errors, because with *considerable* extra
     // configuration it ends up including many files which are *not* valid and