Consider polyfill solution to allow wp-scripts upgrades
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 66
- Forks
- 36
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
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:
- 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.
- 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing pull request 2533, the Gutenberg issue 62202, and the wp-scripts v28 changelog linked in the issue. Determine whether a polyfill can preserve the React-based tooling for supported WordPress versions and document or implement a viable approach, including the minimum WordPress version requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100