That’s why Adam Silverstein proposed to replace Browserify with Webpack four months ago.
WordPress contributors made this decision four months ago. They even reached out to the contributors of Webpack for their review.
🏆 After four months of hard work, the ticket finally made it to WordPress core on October 4th, 2017.
🎉 Kudos to the contributors who made it all possible.
🤔 What is a Bundle Manager?
WordPress used to have Browserify to maintain its JS components. Webpack replaced it last week.
Here are some of the qualities of Webpack which made it a more natural choice.
✔︎ Pros of Using Webpack
- Webpack is easy to implement.
- Webpack does not require automation scripts like Gulp or Grunt.
- It has a single configuration file for the entire build process.
- Webpack provides automation tasks like minification out of the box.
- It also supports live reloading.
- And it does all of these tasks without requiring help from the outside scripts.
Do you think it was a smart decision? Let us know in the comments.
SUBSCRIBE TO DEVELOPERS TAKEAWAY!
A Premium Development Newsletter by TheDevCouple! What is TheDevTakeaway?