chore(repo): enable v8 serializer

[FrozenPandaz]

Current Behavior

The V8 serializer was previously disabled via .local.env file setting NX_USE_V8_SERIALIZER=false.

Expected Behavior

With this change, the V8 serializer is now enabled by removing the .local.env file that was disabling it. This allows Nx to use the V8 serializer for improved performance in task serialization.

Related Issue(s)

This is a repository configuration update to enable the V8 serializer.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
nx-dev	Ready	Preview	Oct 30, 2025 3:25pm

[netlify]

✅ Deploy Preview for nx-docs ready!

Name	Link
🔨 Latest commit	28819be
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/69038274c20dda0008fb5889
😎 Deploy Preview	https://deploy-preview-33286--nx-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 28819be

Command	Status	Duration	Result
nx affected --targets=lint,test,test-kt,build,e...	⛔ Cancelled	1h 2m 21s	View ↗
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	1m 53s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	10s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	1s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	<1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-10-30 16:29:00 UTC

[nx-cloud]

Nx Cloud has identified a possible root cause for your failed CI:

The PR changes were minimal and did not modify any application or test code:

• Deleted the .local.env file which contained NX_USE_V8_SERIALIZER=false
• Incremented the "bust" value from 3 to 4 in nx.json (a cache-busting configuration)

The test failures in e2e-next:e2e-ci--src/next-generation.test.ts were not caused by these changes. The root cause was an environment state issue where the local npm registry at http://localhost:4873 could not serve the "wildcard" package dependency.

The error "ERR_PNPM_FETCH_404 GET http://localhost:4873/wildcard: Not Found - 404" indicates that when pnpm tried to install @nx/[email protected] and @nx/[email protected], it encountered a missing transitive dependency. The wildcard package (required by [email protected], which is a dependency of @nx/next) was not available in the local registry.

This failure occurred during test setup in the packageInstall function at ../utils/create-project-utils.ts:464:29, before any test logic executed. The subsequent TypeError about "Cannot read properties of undefined (reading 'originalEnv')" was a cascading failure that happened during test teardown when resetNextEnv tried to access the setup object that was never successfully created.

Since the PR only modified configuration metadata (cache bust value) and removed an environment variable file unrelated to the wildcard package or npm registry configuration, the test failures were caused by the state of the test environment (specifically the local npm registry's package availability) rather than the code changes themselves.

A code change would likely not resolve this issue, so no action was taken.

View in Nx Cloud ↗

_{🎓 To learn more about Self Healing CI, please visit nx.dev}