Below is a summary of the discussion from yesterday’s JavaScript chat (agenda): Introducing a JS module pattern to WordPress
@omarreiss helped lead the discussion and kick-started the conversation by opening a detailed and thoughtful ticket in trac (#40834) which introduces modules, their goals and how we could go about using them in core. The discussion was around considerations specific to WordPress and a need for modularity was mentioned – @westonruter called out this need for the Customizer, see #30277. Ideas for code that could be extracted into modules included quickedit, core date utilities and wp.media.view.FocusManager.
The decision was made to move in the direction of using Webpack (and ES6 imports) as our bundler of choice, and to work first on switching out browserfy in our current build chain.
Choosing a future JavaScript framework
Discussion started on choosing a new framework for use in core. The main frameworks discussed so far were React and Vue. Attendees shared their hope, goals and criteria for choosing a new framework and mentioned: stability, longevity, mature, well-adopted, proven in a WordPress context, accommodating to accessibility requirements,
Source: https://managewp.org/articles/15212/future-javascript-frameworks-for-wordpress
source https://williechiu40.wordpress.com/2017/05/26/future-javascript-frameworks-for-wordpress/
No comments:
Post a Comment