chore: set up nx workspace

[BioPhoton]

feat(nx-cloud): setup nx cloud workspace

This commit sets up Nx Cloud for your Nx workspace, enabling distributed caching and the Nx Cloud GitHub integration for fast CI and improved developer experience.

You can access your Nx Cloud workspace by going to
https://cloud.nx.app/orgs/65d4d8449e4953a5ed64ff4a/workspaces/65d4d862d2adb16a45a4bc7c

Note: This commit attempts to maintain formatting of the nx.json file, however you may need to correct formatting by running an nx format command and committing the changes.

[pkg-pr-new]

Open in StackBlitz

@code-pushup/ci

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/ci@1075

@code-pushup/cli

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/cli@1075

@code-pushup/create-cli

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/create-cli@1075

@code-pushup/models

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/models@1075

@code-pushup/core

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/core@1075

@code-pushup/nx-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/nx-plugin@1075

@code-pushup/coverage-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/coverage-plugin@1075

@code-pushup/eslint-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/eslint-plugin@1075

@code-pushup/js-packages-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/js-packages-plugin@1075

@code-pushup/jsdocs-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/jsdocs-plugin@1075

@code-pushup/lighthouse-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/lighthouse-plugin@1075

@code-pushup/typescript-plugin

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/typescript-plugin@1075

@code-pushup/utils

npm i https://pkg.pr.new/code-pushup/cli/@code-pushup/utils@1075

commit: 124cad2

[github-actions]

Code PushUp

🤨 Code PushUp report has both improvements and regressions – compared current commit 0061380 with previous commit a419aec.

🕵️ See full comparison in Code PushUp portal 🔍

🏷️ Categories

🏷️ Category	⭐ Previous score	⭐ Current score	🔄 Score change
Performance	🔴 31	🔴 32
Code coverage	🟢 90	🟢 90	–
Security	🔴 0	🔴 0	–
Updates	🟡 77	🟡 77	–
Accessibility	🟢 92	🟢 92	–
Best Practices	🟢 100	🟢 100	–
SEO	🟡 61	🟡 61	–
Type Safety	🟢 100	🟢 100	–
Bug prevention	🟢 100	🟢 100	–
Miscellaneous	🟢 100	🟢 100	–
Code style	🟢 100	🟢 100	–
Documentation	🔴 23	🔴 23	–

👍 1 group improved, 👍 4 audits improved, 👎 1 audit regressed, 16 audits changed without impacting score

🗃️ Groups

🔌 Plugin	🗃️ Group	⭐ Previous score	⭐ Current score	🔄 Score change
Lighthouse	Performance	🔴 31	🔴 32

20 other groups are unchanged.

🛡️ Audits

🔌 Plugin	🛡️ Audit	📏 Previous value	📏 Current value	🔄 Value change
Lighthouse	Initial server response time was short	🟥 Root document took 620 ms	🟩 Root document took 520 ms
Lighthouse	Speed Index	🟥 8.8 s	🟥 7.5 s
Lighthouse	First Contentful Paint	🟥 3.1 s	🟥 3.4 s
Lighthouse	Total Blocking Time	🟥 6,810 ms	🟥 3,030 ms
Lighthouse	Time to Interactive	🟥 19.5 s	🟥 17.6 s
Lighthouse	Minimizes main-thread work	🟥 21.1 s	🟥 11.5 s
Lighthouse	JavaScript execution time	🟥 9.5 s	🟥 5.1 s
Lighthouse	Metrics	🟩 100%	🟩 100%
Lighthouse	Largest Contentful Paint	🟥 11.9 s	🟥 13.7 s
Lighthouse	Reduce unused JavaScript	🟥 Potential savings of 614 KiB	🟥 Potential savings of 613 KiB
Lighthouse	Remove duplicate modules in JavaScript bundles	🟥 Potential savings of 91 KiB	🟥 Potential savings of 100 KiB
Lighthouse	Avoids enormous network payloads	🟩 Total size was 2,665 KiB	🟩 Total size was 2,665 KiB
Lighthouse	Reduce unused CSS	🟥 Potential savings of 116 KiB	🟥 Potential savings of 116 KiB
Lighthouse	Uses efficient cache policy on static assets	🟨 31 resources found	🟨 31 resources found
Lighthouse	Max Potential First Input Delay	🟥 1,800 ms	🟥 1,710 ms
Lighthouse	Server Backend Latencies	🟩 170 ms	🟩 230 ms
Lighthouse	Network Round Trip Times	🟩 10 ms	🟩 60 ms
Lighthouse	Avoids an excessive DOM size	🟥 2,285 elements	🟥 2,283 elements
JS Packages	Outdated NPM dev dependencies.	🟨 56 outdated package versions (30 major, 21 minor, 5 patch)	🟨 57 outdated package versions (30 major, 21 minor, 6 patch)
Code coverage	Branch coverage	🟨 86.1 %	🟨 86.1 %
Lighthouse	Cumulative Layout Shift	🟩 0	🟩 0.001

589 other audits are unchanged.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 124cad2

Command	Status	Duration	Result
nx affected -t e2e-test --parallel=1	✅ Succeeded	11m 2s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-08-22 06:35:23 UTC

[hoebbelsB]

cache is configured as read-write at the moment. So CI & all contributors write to the cache.

if you want to limit access, we have to change that setting and everyone needs to npx nx login in order to write into cache

[matejchalk]

cache is configured as read-write at the moment. So CI & all contributors write to the cache.

if you want to limit access, we have to change that setting and everyone needs to npx nx login in order to write into cache

Good to know! Yes, default should not be read-write, I'll change that. Reading the Nx Cloud docs on GitHub Actions integration, sounds like the best way is to use environment secrets, so that read-write token is used only for protected branches (main) and read-only token is used for unprotected branches (PRs). I'll set that up.

[BioPhoton]

Thx for setting up and adding the NX_CLOUD_ACCESS_TOKEN

[matejchalk]

Looks like the access token is being applied properly in CI. Logs show remote cache was used, and Nx Cloud shows "read access token used".

Let's merge and see if it uses read-write in main branch.