WPBones v2 — Gulp is gone, webpack is in, one command to migrate

Hey everyone! WPBones v2.0 just dropped — the biggest release since the framework launched. Here’s the short version:
The old build pipeline is gone. No more Gulp, no more run-s, no more per-plugin build scripts that drift over time. v2 replaces everything with a single webpack.config.js that auto-discovers your entries from resources/assets/. Drop a .tsx file, webpack picks it up. That’s it.
Every plugin now speaks the same 5 commands:
yarn dev # watch mode
yarn build # production build
yarn test # Jest
yarn format # Prettier
yarn lint # ESLint (WP preset)TypeScript, Jest, Prettier — all configured out of the box. No opt-in, no separate setup. Strict TS, @wordpress/* presets, everything wired and ready.
One-command migration from v1:
composer require wpbones/wpbones:^2.0.1
php bones migrate:to-v2
yarn install && yarn buildThe migrator rewrites your plugin in place — removes gulpfile.js, creates the webpack/TS/Prettier configs, swaps dependencies. We tested it on all 14 official boilerplates.
Other highlights:
php bones make:app now blocks reserved WordPress core handles (no more silent bugs)
14 boilerplates re-released at v2.0.0, each with a dedicated docs page
Full docs refresh at wpbones.com — new migration guide, boilerplates section, WordPress environments comparison
v2.0.1 hotfix already out for an inline-scripts routing edge case
If you’re building WordPress plugins and want Laravel-style patterns (IoC, service providers, Blade, Eloquent) with a modern JS toolchain — give it a try: https://wpbones.com
Migration guide: https://wpbones.com/docs/migrating-to-v2
GitHub: https://github.com/wpbones/WPBones
Discord: https://discord.gg/5bdVyycU8F
Questions? Drop them here — happy to help with the migration!



Replies