Skip to content

Consider polyfill solution to allow wp-scripts upgrades #2624

Open

Description

@acicovic

Is your feature request related to a problem?

When we attempted to upgrade to wp-scripts v28, our tooling based on React disappeared. This was experienced by others as well, and the main issue is here.

Apparently, there are 2 propositions:

  1. Don't upgrade to wp-scripts v28 until the minimum WP version for the plugin is 6.6. This is what's officially proposed in the changelog and related article.
  2. There's a mention of using a polyfill solution.

Describe the solution you'd like

For now, we've paused dependabot updates for v28.

Although this is what's officially proposed, the first proposition's viability isn't a given in my opinion. If a polyfill solution is implementable, we should look into this possibility. It seems that the polyfill solution will require updating our minimum WP version to at least 5.9, which shouldn't be an issue.

Activity

  1. added this to the Future Milestone milestone on Jul 10, 2024
  2. modified the milestones: Future Milestone, on Jul 19, 2024
  3. acicovic commented on Jul 24, 2024

    @acicovic
    CollaboratorAuthor

    Let's remember to remove "@typescript-eslint/method-signature-style": "error" from .eslintrc when we're done with this.

  4. acicovic commented on Sep 20, 2024

    @acicovic
    CollaboratorAuthor

    Seems that we're blocked for the time being. See WordPress/gutenberg#62202 (comment).

  5. modified the milestones: , Future Milestone on Mar 18, 2025
  6. added theissue type on May 22, 2025
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

    Maintenance & FixesTicket/PR related to codebase maintenance taskswp-parselyRequired label for all issues

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions