Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Update Test Schema: First-party Dependency Scan

Open
  • Is something wrong?
#661 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
data

Research direction

Start with the shared schema introduced by PR #647 and the result generation, validation, persistence, and consumer paths for this test. Extend TestBaseSchema with the exact first-party dependency and duplicate counts, and include name, framework, and packagePath. Check which historical records contain enough data to migrate; document the chosen handling for records that cannot be converted, and verify the updated schema and results.

Written by the indexing model from the issue text.

Description

documentation

Update this test's schema to use the shared base or benchmark schema introduced in https://github.com/e18e/framework-tracker/pull/647.

Scope: first-party dependency counts and duplicate counts.

Extend TestBaseSchema for this exact-value scan. Keep its exact outputs as test-specific fields.

Include the required test identity fields: name, framework, and packagePath. Update result generation, validation, persistence, and consumers as needed.

Where historical test data is available, convert past records to the new schema. Where the required data is unavailable, use the new schema going forward; do not invent missing measurements or iterations.

As a last resort, if the historical schema cannot reasonably be migrated, consider dropping affected past records or re-running the test using the dependency snapshots retained in the main test records/schema. Document the chosen approach.

Blocked by #647, the shared-schema part of #633.

Part of #633

Dominant language
TypeScript
Stars
42
Forks
16
Avg merge
13h 41m
Merged PRs (30d)
144

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from e18e/framework-tracker

All issues in e18e/framework-tracker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.