Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Deprecate grunt-patch-wordpress

Open
#70 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, wordpress

Research direction

No file or test path is named; begin by inventorying the package configuration, Grunt entry points, and current Mocha tests. Review the requested Jest and WordPress Gutenberg migration boundaries, then clarify whether this repository becomes a thin Grunt wrapper; done requires an agreed successor and validated migration plan.

Written by the indexing model from the issue text.

Description

grunt-patch-wordPress has been an amazing tool, but it's time for it to move on. In order to do that, we need to get a successor in place. For that, we need to:

  1. Remove the grunt dependency
  2. Migrate the tests from mocha to jest ( see: https://gziolo.pl/2017/10/25/migrating-to-jest-test-runner/ )
  3. Use the wordpress/gutenberg scripts and styles
  4. Move the codebase over to wordpress/gutenberg
  5. ???
  6. Celebate the future.

It's possible that this repo can serve as a thin grunt wrapper around the replacement script.

Dominant language
JavaScript
Stars
51
Forks
13
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/grunt-patch-wordpress

All issues in WordPress/grunt-patch-wordpress

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.