Skip to content

feat: add SolidJS data anomalies to download-anomalies.data.ts - #2661

Merged
graphieros merged 1 commit into
npmx-dev:mainfrom
gameroman:update-solid-js-data
May 2, 2026
Merged

feat: add SolidJS data anomalies to download-anomalies.data.ts#2661
graphieros merged 1 commit into
npmx-dev:mainfrom
gameroman:update-solid-js-data

Conversation

@gameroman

Copy link
Copy Markdown
Member

🔗 Linked issue

🧭 Context

📚 Description

@vercel

vercelBot commented Apr 30, 2026

Copy link
Copy Markdown
Contributor

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

ProjectDeploymentActionsUpdated (UTC)
npmx.devReadyReadyPreview, CommentApr 30, 2026 7:20am
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
docs.npmx.devIgnoredIgnoredPreviewApr 30, 2026 7:20am
npmx-lunariaIgnoredIgnoredApr 30, 2026 7:20am

Request Review

@coderabbitai

coderabbitaiBot commented Apr 30, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Extended anomaly dataset with updated download metrics for package tracking.

Walkthrough

A new download anomaly entry for the solid-js package is added to the DOWNLOAD_ANOMALIES data array. The entry includes a specific date range and weekly download statistics ranging from 21,395 to 28,308 downloads.

Changes

Cohort / File(s)Summary
Download Anomalies Data
app/utils/download-anomalies.data.ts
New DownloadAnomaly object appended to the DOWNLOAD_ANOMALIES array for the solid-js package with date range and weekly download metrics.
🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check nameStatusExplanationResolution
Description check⚠️ WarningThe description field contains only the repository's PR template with no actual content relating to the changeset, failing to provide meaningful context about the change.Provide a substantive description explaining why SolidJS data anomalies were added, what problem this solves, and any relevant context or linked issues.
✅ Passed checks (3 passed)
Check nameStatusExplanation
Title check✅ PassedThe title clearly and specifically describes the main change: adding SolidJS data anomalies to the download-anomalies.data.ts file, matching the changeset.
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitaicoderabbitaiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
app/utils/download-anomalies.data.ts (1)

25-29: ⚡ Quick win

Add a short rationale comment before this new anomaly block.

Line 25 adds a new entry without the explanatory comment requested by the file note (Line 33). Please add a one-liner describing why this solid-js period is considered anomalous.

Suggested patch
+ // solid-js holiday-period download spike anomaly
{
packageName: 'solid-js',
start: { date: '2024-12-22', weeklyDownloads: 21_395 },
end: { date: '2024-12-24', weeklyDownloads: 28_308 },
},
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@app/utils/download-anomalies.data.ts` around lines 25 - 29, Add a one-line
rationale comment immediately above the anomaly object where packageName is
'solid-js' explaining why this period is anomalous (e.g., "Notable jump in
weeklyDownloads from 21,395 to 28,308 between 2024-12-22 and 2024-12-24"), so
readers of download-anomalies.data.ts can see the reason for the entry; place
the comment directly before the object entry to match the existing file note on
line 33.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@app/utils/download-anomalies.data.ts`:
- Around line 25-29: Add a one-line rationale comment immediately above the
anomaly object where packageName is 'solid-js' explaining why this period is
anomalous (e.g., "Notable jump in weeklyDownloads from 21,395 to 28,308 between
2024-12-22 and 2024-12-24"), so readers of download-anomalies.data.ts can see
the reason for the entry; place the comment directly before the object entry to
match the existing file note on line 33.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bee24343-dd54-414d-9564-5cb26fffb599

📥 Commits

Reviewing files that changed from the base of the PR and between 5eab00c and b29a99d.

📒 Files selected for processing (1)
  • app/utils/download-anomalies.data.ts

@codecov

codecovBot commented Apr 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@graphieros
graphieros added this pull request to the merge queueMay 2, 2026
Merged via the queue into npmx-dev:main with commit 1cd4f82May 2, 2026
23 checks passed
@github-actionsgithub-actionsBot mentioned this pull request May 2, 2026
@gameroman
gameroman deleted the update-solid-js-data branch May 3, 2026 09:01
ayo-run pushed a commit to ayo-run/npmx.dev that referenced this pull request Aug 5, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@gameroman@graphieros