Skip to content

[External Plugin]: jquery-to-react #6221

New issue
New issue
Closed
Closed
[External Plugin]: jquery-to-react#6221
Labels
external-pluginPublic external plugin submissionrejectedSubmission was rejected by a maintainerthird party

Description

@EmmanuellDev
EmmanuellDev
opened on Nov 3, 2026

Plugin name

jquery-to-react

Short description

Migrate jQuery apps and pages to React — full rewrites or incremental strangler-fig migrations of any size, including jQuery plugins and jQuery UI.

GitHub repository

cobuild-tech/cbx-plugins

Plugin path inside the repository

jquery-to-react

Ref to review

v2.1.0

Commit SHA to review

74aca6579e74a5739783dc00b6d3418c6f48af18

Version

1.2.0

License identifier

MIT

Author name

CobuildX

Author URL

https://github.com/cobuild-tech

Homepage URL

https://github.com/cobuild-tech/cbx-plugins/tree/main/jquery-to-react

Keywords

react, migration, jquery, jquery-ui, jquery-plugins, legacy-javascript, refactoring, modernization

Additional notes for reviewers

Resubmission of #5866. The plugin has changed since that review: this submission pins the new release v2.1.0, and the evaluation evidence ships inside that snapshot.

What changed in v2.1.0 (this plugin is now 1.2.0):

  • Direct mode for the most common request, "convert this part of my repo to React". The skill reads its framework references, searches the rest of the repo for code that depends on the area, and ends with a list of every behavior difference.
  • A framework-specific coupling checklist, always applied, covering the implicit behavior that migrations break (details below).
  • Broader triggers for "rewrite / rebuild / replace … with React" requests.

Evaluation, at the pinned snapshot. The same model (Claude Sonnet), the same repository, and the same prompt, with and without the plugin. There are 25 multi-file cases across the five sibling plugins, 5 of them for this framework. Each case has 6 pass/fail criteria, written before any run and kept hidden from the model. Grading is blind to which run used the plugin.

Without plugin With plugin
This framework 28/30 30/30
All five plugins 138/150 145/150

Examples from this framework:

  • 05-autosave-serialize (Autosave form posting .serialize() data to a Rails controller): Kept PATCH and the X-Requested-With: XMLHttpRequest header that $.ajax sends. Without the plugin, fetch dropped the header without mention.
  • 02-booking-form-plugins (Booking form with jQuery UI datepicker, jquery-validate, and ajaxComplete re-initialization): Scoped the page-wide widget re-initialization away from the React form and listed every validation and timing difference.

Every run's diff, final answer, and per-criterion grade with its reason are in evals/results/. Also see results · method · cases · runner.

Domain-specific constraints this plugin encodes for jQuery apps and pages, including jQuery plugins and jQuery UI (one reference file per area under skills/cobuildx-ai-jquery-to-react-migration/references/):

  • Detects the setup first: jQuery version and whether jQuery Migrate is loaded, CDN global $ vs bundled, server-rendered pages (Rails, Django, PHP, JSP) vs SPA, and every plugin / jQuery UI widget with where it is created and destroyed.
  • State hidden in the DOM. Classes, data-*, .data(), hidden inputs and text that later code reads back are listed and turned into explicit state.
  • Delegated handlers. $(document).on('click', '.x', …) handlers are ported without changing which elements respond or the event order.
  • $.ajax and animation. Global ajaxSetup/ajaxSend hooks (CSRF headers, auth), deferred/promise chains, and animate/fadeIn timing that callers wait on.
  • Plugins. Each jQuery plugin or jQuery UI widget is replaced with a React library or wrapped in a ref-owned component with proper destroy.
  • One owner per element. Once React owns a container, no jQuery touches it; the skill enforces this during the incremental phase.

Specialized workflow, not just advice:

  • Resumable state across sessions. A .migration/ folder in the user's repo holds the unit list, route map, per-unit status and QA gates, so "continue the migration" or "what's left?" works in a new session without re-reading the codebase.
  • Strategy selection. Full rewrite vs strangler-fig vs branch-by-abstraction, chosen from app size and risk, with an explicit cutover plan.
  • Read-only jquery-inventory agent that maps routes, components, services, data layer and hidden wiring before any code changes.
  • Read-only jquery-parity-reviewer agent that checks each ported unit against the original for behaviour, markup, data and timing differences before the old code may be deleted.
  • /plan command that writes the plan without touching app code.

Pins tag v2.1.0 and its full commit SHA. Free, MIT licensed, no telemetry, sign-up, or paid service. The bundled Context7 MCP server is the public endpoint and needs no credentials. This is one of five sibling plugins (ember, angular, backbone, jquery, and vanillajs to React), each with its own framework-specific references, submitted separately.

Submission checklist

  • The plugin lives in a public GitHub repository.
  • The ref and/or sha I provided is immutable (release tag and/or full 40-character commit SHA), not a branch.
  • This submission follows this repository's contribution, security, and responsible AI policies.
  • This plugin is not already listed in the Awesome Copilot marketplace.

Activity

  1. github-actions
    added
    awaiting-reviewSubmission is waiting for automated intake validation
    external-pluginPublic external plugin submission
    ready-for-reviewSubmission passed intake validation and is ready for maintainer review
    third party
    and removed
    awaiting-reviewSubmission is waiting for automated intake validation
    on Nov 3, 2026

  2. github-actions commented on Nov 3, 2026

    @github-actions
    github-actionsBot
    on Nov 3, 2026 – with GitHub Actions
    Contributor

    ✅ External plugin intake passed

    This submission passed automated intake validation and quality checks and is ready for maintainer review.

    View workflow run · Download full quality gate logs

    Reviewer signals

    These are non-blocking heuristics for maintainer review; they are not evidence of misconduct or low quality.

    Signal Result
    Repository owner Organization-owned (third party)
    Repository age 28 day(s)
    Repository activity 0 stars; 0 forks
    Repository counts 0 stars · 1 watchers · 0 forks · 2 open issues/PRs
    Homepage heuristics ⚠️ pricing, checkout

    Quality gate summary

    Legend: ✅ pass · ⚠️ warning · 🛑 fail

    Gate Status
    spec compliance ✅ pass
    vally lint ✅ pass
    install smoke test ✅ pass
    version match ✅ pass
    ref/sha consistency ✅ pass
    canvas structure ⚪ not_run
    • spec compliance: pass
    • vally lint: pass
    • install smoke test: pass
    • version match: pass
    • ref/sha consistency: pass
    • canvas structure: not_run
    • overall: pass
    spec compliance output (✅ pass) 
    Agent Plugins v1.0.0 manifest checks passed for plugin.json.
    vally lint output (✅ pass) 
    ✅ cobuildx-ai-jquery-to-react-migration (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed
    install smoke test output (✅ pass) 
    Install smoke test succeeded. Verified /tmp/external-plugin-quality-QbrzlC/copilot-home/.copilot/installed-plugins/external-plugin-intake/jquery-to-react/plugin.json.
    Version match output 
    - v2.1.0: matched version "1.2.0" at "jquery-to-react/plugin.json".
- 74aca6579e74a5739783dc00b6d3418c6f48af18: matched version "1.2.0" at "jquery-to-react/plugin.json".
    Ref/SHA consistency output 
    source.ref "v2.1.0" resolves to the same commit as source.sha "74aca6579e74a5739783dc00b6d3418c6f48af18".
    Canvas structure output 
    Canvas structure gate skipped because plugin is not tagged with "canvas".

    Canonical external.json payload

    {
  "name": "jquery-to-react",
  "description": "Migrate jQuery apps and pages to React — full rewrites or incremental strangler-fig migrations of any size, including jQuery plugins and jQuery UI.",
  "version": "1.2.0",
  "author": {
    "name": "CobuildX",
    "url": "https://github.com/cobuild-tech"
  },
  "repository": "https://github.com/cobuild-tech/cbx-plugins",
  "homepage": "https://github.com/cobuild-tech/cbx-plugins/tree/main/jquery-to-react",
  "license": "MIT",
  "keywords": [
    "react",
    "migration",
    "jquery",
    "jquery-ui",
    "jquery-plugins",
    "legacy-javascript",
    "refactoring",
    "modernization"
  ],
  "source": {
    "source": "github",
    "repo": "cobuild-tech/cbx-plugins",
    "path": "jquery-to-react",
    "ref": "v2.1.0",
    "sha": "74aca6579e74a5739783dc00b6d3418c6f48af18"
  }
}

  3. aaronpowell commented on Nov 4, 2026

    @aaronpowell
    aaronpowell
    on Nov 4, 2026
    Contributor

    /reject This is substantially the plugin rejected in #5866, plus a Direct mode, a coupling checklist, and new global-AJAX references. Your own evals show the model without the plugin already passes all six global-AJAX criteria (CSRF, 401 redirect, ajaxStart/Stop, cache: false), scoring 28/30. Both gains came from listing behaviour differences in the final summary, which a one-line prompt achieves. Your pilot also showed the previously submitted version scoring below no plugin (22 vs 28). All runs were single-shot in Claude Code, not Copilot. This still doesn't demonstrate meaningful model uplift.

  4. github-actions
    added
    rejectedSubmission was rejected by a maintainer
    and removed
    ready-for-reviewSubmission passed intake validation and is ready for maintainer review
    on Nov 4, 2026

  5. github-actions commented on Nov 4, 2026

    @github-actions
    github-actionsBot
    on Nov 4, 2026 – with GitHub Actions
    Contributor

    ❌ External plugin rejected

    A maintainer rejected jquery-to-react, and the submission issue has been closed.

    Reason

    This is substantially the plugin rejected in #5866, plus a Direct mode, a coupling checklist, and new global-AJAX references. Your own evals show the model without the plugin already passes all six global-AJAX criteria (CSRF, 401 redirect, ajaxStart/Stop, cache: false), scoring 28/30. Both gains came from listing behaviour differences in the final summary, which a one-line prompt achieves. Your pilot also showed the previously submitted version scoring below no plugin (22 vs 28). All runs were single-shot in Claude Code, not Copilot. This still doesn't demonstrate meaningful model uplift.

    This issue is now closed and /rerun-intake will no longer reopen it. If you address the feedback, please open a new external plugin submission issue.

  6. github-actions
    closed this as completedon Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    external-pluginPublic external plugin submissionrejectedSubmission was rejected by a maintainerthird party

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions