fix: error build if fixture typechecking fails (#78839)

The type checking introduced in #75935 wasn't actually failing the
build, because `find ... -exec ...` seems to eat non-zero exit codes.
This is fixed by using `xargs` instead.

Also fixes some files that were failing typechecking but no one noticed
due to the above bug.

Author: lubieowoce

crates/next-custom-transforms/tests/fixture/server-actions/modules.d.ts

@@ -49,3 +49,6 @@ declare module 'components' {
 declare module 'navigation' {
   export function redirect(href: string): void
 }
+
+// Some tests generate `data:text/javascript,...` imports
+declare module 'data:text/*'

crates/next-custom-transforms/tests/fixture/server-actions/tsconfig.json

@@ -29,6 +29,8 @@
     "./server-graph/25/output.js",
     "./server-graph/28/output.js",
     "./server-graph/30/output.js",
+    // FIXME: buggy renaming of anonymous functions
+    "./server-graph/51/output.js",
     // Excluded because of weird TS behavior around `action.bind(...)` making args optional
     // (but only if no JSDoc type annotations are present)
     "./server-graph/24/output.js"

package.json

@@ -43,7 +43,7 @@
     "lint-ast-grep": "ast-grep scan",
     "lint-no-typescript": "run-p prettier-check lint-eslint lint-language",
     "types-and-precompiled": "run-p lint-typescript check-precompiled check-compiler-fixtures types:test-lib",
-    "check-compiler-fixtures": "find crates/next-custom-transforms/tests/fixture -type f -name 'tsconfig.json' -exec /bin/sh -c 'echo \"project: $1\"; pnpm tsc --noEmit --project \"$1\"' -- {} \\;",
+    "check-compiler-fixtures": "find crates/next-custom-transforms/tests/fixture -type f -name 'tsconfig.json' -print0 | xargs --null -n1 -I'{}' pnpm tsc --noEmit --project '{}'",
     "validate-externals-doc": "node ./scripts/validate-externals-doc.js",
     "lint": "run-p test-types lint-typescript prettier-check lint-eslint lint-ast-grep lint-language",
     "lint-fix": "pnpm prettier-fix && pnpm lint-eslint --fix",