docs: refresh home stats for oxlint, vite, and vitest Issue: #1511 by nozomee · Pull Request #1512 · voidzero-dev/vite-plus

nozomee · 2026-05-04T06:12:55Z

Changes made

1. `docs/.vitepress/theme/components/home/FeatureCheck.vue`

ESLint rule count (Vite+ check section): 600+ → 750+ (text before the ESLint code span).

2. `docs/.vitepress/theme/components/home/ProductivityGrid.vue`

“A trusted stack to standardize on” — Vite

Weekly npm downloads: 69m+ → 115m+
GitHub stars: 78.7k → 80.4k

Vitest

Weekly npm downloads: 35m+ → 57m+
GitHub stars: 16.1k → 16.5k

OXC (npm row uses oxlint package downloads)

Weekly npm downloads: 5m+ → 5.3m+
GitHub stars: 19.8k → 21.0k

Files touched: 2
Net: 7 lines updated (string substitutions only; no logic or layout changes).

netlify · 2026-05-04T06:13:01Z

✅ Deploy Preview for viteplus-preview ready!

Name	Link
🔨 Latest commit	`a453a70`
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/69fb61d78259600008ea7204
😎 Deploy Preview	https://deploy-preview-1512--viteplus-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

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

jong-kyung

LGTM

mdong1909 · 2026-05-04T09:00:42Z

We want a way to automate the npm downloads & github stars. Otherwise the hard coded numbers will be outdated quickly. For example, vitest had 7% increase in downloads in the last week.

A potential way to do this is to have a fetch data script that is executed on a schedule via github actions. The data is stored as a json in this repo, which the home pages references

nozomee · 2026-05-04T09:27:03Z

I’d like to take this on — I’m already actively working on it and will open a PR soon.

Right now the trusted-stack numbers on the homepage are hard-coded, which means they’ll drift quickly and require repeated manual edits over time (especially with npm download velocity changing week-to-week).

My planned implementation:

Add a lightweight fetch script that pulls:
Weekly npm downloads for Vite / Vitest / OXC
GitHub stars for their corresponding repos
Store that data in a committed JSON file inside the docs theme as the single source of truth
Replace hard-coded homepage values with JSON-driven values at build time
Add a scheduled GitHub Action (weekly + manual dispatch) that refreshes the JSON automatically and only commits when values actually change

Why this should help:

Keeps homepage metrics current automatically
Preserves the static-site model (no client-side API calls)
Avoids recurring hand-edits
Keeps changes transparent in git history
Contributors won’t need to do anything extra unless they specifically want an immediate local refresh
In the normal case, maintainers shouldn’t need to manually update stats either—the scheduled workflow handles it

Expected flow after merge:

Merge once
Workflow refreshes stats automatically on schedule
Homepage numbers stay fresh with near-zero maintenance
Manual command is only for immediate refreshes or branch-protection fallback

A few maintainer decisions may still be useful:

Whether github-actions[bot] should push JSON-only updates directly to main or use PRs
Preferred refresh cadence
Whether oxlint remains the best npm proxy for OXC

In short: automate the trusted-stack stats pipeline once, remove repetitive manual maintenance, and keep homepage credibility high with minimal long-term overhead. PR coming soon.

nozomee · 2026-05-04T09:38:38Z

@jong-kyung @mdong1909 I’ve committed the changes to address these updates, Kindly review it once!

jong-kyung · 2026-05-04T09:44:51Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 23b81b2815

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

…o node-version-file: .node-version

nozomee · 2026-05-04T12:05:51Z

@jong-kyung @mdong1909 I’ve committed the changes , Kindly review it once!

…and TypeScript migration

nozomee · 2026-05-04T18:33:23Z

@jong-kyung @camc314 I’ve committed the changes , Kindly review it once!

jong-kyung · 2026-05-05T08:50:33Z

@codex review

chatgpt-codex-connector · 2026-05-05T08:53:50Z

Codex Review: Didn't find any major issues. Breezy!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

jong-kyung · 2026-05-05T09:23:09Z

Could this script live under .github/scripts/?
It's CI-only and uses the same peter-evans/create-pull-request pattern as upgrade-deps.yml.

jong-kyung · 2026-05-05T09:23:50Z

@nozomee Could you take a look at the failing CI?

…ocs lockfile - Relocate fetch script to .github/scripts and update references - Fix docs deps (no catalog:), update docs pnpm-lock - Adjust docs scripts tsconfig for node/dom types

socket-security · 2026-05-05T16:17:55Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/typescript@6.0.3

View full report

nozomee · 2026-05-05T16:25:49Z

@jong-kyung I’ve committed the changes , Kindly review it once!

jong-kyung · 2026-05-06T00:26:23Z

+      - name: Fetch npm and GitHub stats
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: node docs/scripts/fetch-trusted-stack-stats.ts


The script lives at .github/scripts/fetch-trusted-stack-stats.ts, not docs/scripts/.

Good catch — you’re right.

I moved the fetch script to /.github/scripts/fetch-trusted-stack-stats.ts to align with the existing CI scripts (similar to upgrade-deps.yml). I’ve updated the workflow step to run:

node .github/scripts/fetch-trusted-stack-stats.ts

so it matches the actual location.

will push the changes shortly!

jong-kyung · 2026-05-06T01:03:13Z

Is this file actually needed? The root tsconfig.json already enables the same options

Root tsconfig.json isn’t a good fit because it lacks DOM lib (needed for fetch) and would typecheck too much of the repo. I moved the minimal config to .github/scripts/tsconfig.json (since it’s for CI scripts) and updated the docs check script to use it; removed docs/scripts/tsconfig.json, will push the commit changes shortly.

Root tsconfig.json isn’t a good fit because it lacks DOM lib (needed for fetch)

This script shouldn't rely on DOM lib since it'll be executing in a node env.

Root tsconfig.json isn’t a good fit because it lacks DOM lib (needed for fetch)

This script shouldn't rely on DOM lib since it'll be executing in a node env.

Good point — agreed. Even though the script uses fetch, it runs in Node, so it shouldn’t depend on the DOM lib.

jong-kyung · 2026-05-06T01:05:41Z

Are these two new devDependencies actually needed here? @types/node and typescript are already provided by the workspace root.

I looked into this, and with our current setup it’s not really safe to remove those dependencies.

Even though typescript and @types/node exist at the workspace root, the docs/ directory is installed and locked independently (pnpm -C docs install --frozen-lockfile with its own docs/pnpm-lock.yaml). That means docs/ won’t reliably inherit root devDependencies unless we switch to a full workspace-level install.

Since docs/ also runs its own TypeScript check (update-trusted-stack-stats:check), it needs local access to tsc plus Node typings for imports and globals.

So for now, keeping typescript and @types/node in docs/package.json makes the most sense — it keeps docs/ self-contained and avoids CI or isolated install issues.

If we want to remove that duplication later, we’d first need to change the install/CI flow to rely on a root workspace install rather than pnpm -C docs.

I think we can simplify further: the :check script isn't wired into any CI job, so it's not actually catching anything.

Could we drop:

docs/scripts/tsconfig.json

The update-trusted-stack-stats(:check) scripts in docs + root

@types/node and typescript from docs/devDependencies

cc. @camc314 WDYT?

Good point — let’s see what @camc314 thinks first, then we can figure out the best path forward from there.
Happy to help once we’ve got their input.

- Update update-trusted-stack-stats workflow to use correct script path - Move stats typecheck tsconfig under .github/scripts and remove docs/scripts/tsconfig.json - Keep docs check script pointing to the new tsconfig

nozomee · 2026-05-06T15:55:59Z

@jong-kyung Looks like this is only a packageManager version conflict (10.33.0 vs 10.33.2). Could you check which version we want to standardize on across the repo/CI and align this accordingly? Once we confirm the intended pnpm version, we can resolve it cleanly.

jong-kyung · 2026-05-07T00:37:13Z

@nozomee On pnpm: let's stick with 10.33.0 as pinned in package.json.

That said — the version mismatch you're seeing is really a lockfile drift issue, not a pnpm version issue. It only exists because docs/package.json gained typescript and @types/node, which forced docs/pnpm-lock.yaml to be regenerated.

If we go with the simplification (drop :check script, tsconfig, and the two devDependencies), the docs lockfile change goes away entirely and this pnpm question becomes moot.
I'd still lean toward that direction since the :check script isn't wired into CI.

cc. @camc314

docs: refresh home stats for oxlint, vite, and vitest

ed939b2

nozomee changed the title ~~docs: refresh home stats for oxlint, vite, and vitest #1511~~ docs: refresh home stats for oxlint, vite, and vitest Issue: #1511 May 4, 2026

nozomee mentioned this pull request May 4, 2026

docs: update stats in home page #1511

Open

4 tasks

jong-kyung approved these changes May 4, 2026

View reviewed changes

jong-kyung requested a review from mdong1909 May 4, 2026 06:35

feat(docs): automate trusted stack stats via JSON and workflow

23b81b2

chatgpt-codex-connector Bot reviewed May 4, 2026

View reviewed changes

Comment thread docs/scripts/fetch-trusted-stack-stats.mjs Outdated

jong-kyung reviewed May 4, 2026

View reviewed changes

Comment thread docs/.vitepress/env.d.ts Outdated

Comment thread .github/workflows/update-trusted-stack-stats.yml Outdated

jong-kyung self-assigned this May 4, 2026

Removed the declare module '*.json' block from env.d.ts. & switched t…

b1ef0af

…o node-version-file: .node-version

Dropped generatedAt from trusted-stack-stats.json

55163f2

jong-kyung approved these changes May 4, 2026

View reviewed changes

camc314 reviewed May 4, 2026

View reviewed changes

Comment thread .github/scripts/fetch-trusted-stack-stats.ts

camc314 reviewed May 4, 2026

View reviewed changes

Comment thread .github/workflows/update-trusted-stack-stats.yml

refactor(ci): secure trusted stack stats automation with PR workflow …

93be819

…and TypeScript migration

jong-kyung reviewed May 5, 2026

View reviewed changes

refactor(docs): move trusted-stack stats fetcher to .github and fix d…

29b39bb

…ocs lockfile - Relocate fetch script to .github/scripts and update references - Fix docs deps (no catalog:), update docs pnpm-lock - Adjust docs scripts tsconfig for node/dom types

jong-kyung reviewed May 6, 2026

View reviewed changes

fix(ci): align trusted stack stats typecheck + workflow script paths

a453a70

- Update update-trusted-stack-stats workflow to use correct script path - Move stats typecheck tsconfig under .github/scripts and remove docs/scripts/tsconfig.json - Keep docs check script pointing to the new tsconfig

Conversation

nozomee commented May 4, 2026

Changes made

1. docs/.vitepress/theme/components/home/FeatureCheck.vue

2. docs/.vitepress/theme/components/home/ProductivityGrid.vue

Uh oh!

netlify Bot commented May 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for viteplus-preview ready!

Uh oh!

jong-kyung left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mdong1909 commented May 4, 2026

Uh oh!

nozomee commented May 4, 2026

Uh oh!

nozomee commented May 4, 2026

Uh oh!

jong-kyung commented May 4, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

nozomee commented May 4, 2026

Uh oh!

Uh oh!

Uh oh!

nozomee commented May 4, 2026

Uh oh!

jong-kyung commented May 5, 2026

Uh oh!

chatgpt-codex-connector Bot commented May 5, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jong-kyung commented May 5, 2026

Uh oh!

socket-security Bot commented May 5, 2026

Uh oh!

nozomee commented May 5, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nozomee May 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nozomee commented May 6, 2026

Uh oh!

jong-kyung commented May 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1. `docs/.vitepress/theme/components/home/FeatureCheck.vue`

2. `docs/.vitepress/theme/components/home/ProductivityGrid.vue`

netlify Bot commented May 4, 2026 •

edited

Loading

jong-kyung left a comment •

edited

Loading

nozomee May 6, 2026 •

edited

Loading