From e000ed80875451e8e1d1dc4519139ab440a5de30 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 5 Jun 2026 16:00:40 +0000
Subject: [PATCH 1/2] Initial plan


From 7b85a2b91ee640f66fc684bebdc54b6a64267408 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 5 Jun 2026 16:05:47 +0000
Subject: [PATCH 2/2] fix: add schematics/package.json to treat compiled
 schematics as CommonJS

The distributed package has "type": "module" (added by ng-packagr), which
causes Node.js to treat all .js files in the package as ES modules. The
schematics are compiled as CommonJS and use `exports`, so running ng-update
fails with "exports is not defined in ES module scope".

Adding a package.json with {"type": "commonjs"} in the schematics directory
tells Node.js to treat those .js files as CommonJS modules, fixing the error.
---
 projects/testing-library/schematics/package.json | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 projects/testing-library/schematics/package.json

diff --git a/projects/testing-library/schematics/package.json b/projects/testing-library/schematics/package.json
new file mode 100644
index 0000000..5bbefff
--- /dev/null
+++ b/projects/testing-library/schematics/package.json
@@ -0,0 +1,3 @@
+{
+  "type": "commonjs"
+}