rspack-webpack-gap-tracker

Audit and update Rspack compatibility gaps against webpack features, plugins, and test coverage.

12.9k|843|Updated Apr 1, 2022
One-click install
npx skills add https://github.com/web-infra-dev/rspack --skill rspack-webpack-gap-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rspack-webpack-gap-tracker
Source: https://github.com/web-infra-dev/rspack/tree/main/.agents/skills/rspack-webpack-gap-tracker
Command: npx skills add https://github.com/web-infra-dev/rspack --skill rspack-webpack-gap-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires zx, diff, prettier, and includes scripts (resource) components.

What problem does it solve?

Keeping Rspack's webpack compatibility tracking issue accurate requires manually comparing webpack releases, config schemas, built-in plugins, and thousands of test cases, which is slow and error-prone.

Core Features & Use Cases

  • Gap Auditing: Systematically find missing webpack features by comparing releases, config schemas, built-in plugins, and ecosystem plugins against Rspack.
  • Test Directory Diffing: Run the bundled zx script to compare webpack test suites (cases, configCases, statsCases, etc.) against Rspack's rspack-test directories, with optional Prettier-normalized content diffs.
  • Structured Issue Updates: Update the tracking issue, completed-feature comment, and missing-test comment using consistent checklist entry formats with timestamps.
  • Use Case: After a new webpack release, ask the agent to audit new features, classify each gap as recommended, pending, or not recommended for Rspack, and update the tracking issue without duplicating existing entries.

Quick Start

Use the rspack-webpack-gap-tracker skill to audit webpack features released since the last update and refresh the compatibility tracking issue.

Frequently Asked Questions about rspack-webpack-gap-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare webpack and Rspack test directories?

Run the bundled diff-tests script with pnpm --filter @rspack/skill-webpack-gap-tracker diff-tests -- --webpack /path/to/webpack. It maps webpack test suites like cases and statsCases to Rspack's normalCases and statsOutputCases and lists tests missing on either side.

How do I track Rspack compatibility gaps against webpack?

Read the main tracking issue and its comments, then search webpack releases, config schemas, built-in plugins, and merged Rspack PRs for new gaps. Record each gap as a checklist entry classified as recommended, pending, or not recommended, avoiding duplicates with existing entries.

Can I diff file contents of shared webpack and Rspack test cases?

Yes, pass --content with a positional filter to emit unified diffs for test cases present in both repositories. Files are normalized with a deterministic Prettier configuration first, and webpack.config and rspack.config files are treated as the same logical file.

Where are native CSS compatibility gaps recorded?

Native CSS-related gaps are recorded in the dedicated tracking issue #14002 instead of the main compatibility issue #14556. This keeps CSS-specific work separated from general webpack feature parity tracking.

When should a webpack feature gap be marked not recommended for Rspack?

Mark a gap not recommended when it can be implemented outside Rspack without native Rust work or performance impact, such as via a third-party package or an Rstack ecosystem plugin. First check whether Rsbuild or rstackjs packages already provide a compatible solution.