Skip to content

Consider polyfill solution to allow wp-scripts upgrades #2624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
acicovic opened this issue Jul 10, 2024 · 2 comments
Open

Consider polyfill solution to allow wp-scripts upgrades #2624

acicovic opened this issue Jul 10, 2024 · 2 comments
Labels
Maintenance Ticket/PR related to codebase maintenance tasks wp-parsely Required label for all issues

Comments

@acicovic
Copy link
Collaborator

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.

@acicovic acicovic added the Maintenance Ticket/PR related to codebase maintenance tasks label Jul 10, 2024
@acicovic acicovic added this to the Future Milestone milestone Jul 10, 2024
@acicovic acicovic modified the milestones: Future Milestone, Summer 2024 Jul 19, 2024
@acicovic
Copy link
Collaborator Author

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

@acicovic
Copy link
Collaborator Author

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

@acicovic acicovic modified the milestones: Summer 2024, Future Milestone Mar 18, 2025
@acicovic acicovic added the wp-parsely Required label for all issues label Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Ticket/PR related to codebase maintenance tasks wp-parsely Required label for all issues
Projects
None yet
Development

No branches or pull requests

1 participant