WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #43055, comment 66


Ignore:
Timestamp:
05/21/2018 03:40:21 PM (11 months ago)
Author:
nbachiyski
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #43055, comment 66

    initial v1  
    1 One forward-facing requirement I’d add is to not depend on `grunt`, `npm`, or `webpack` in the CLI tools or configuration of the new build system – the same way WordPress hasn't depended on any framework, even Gutenberg has abstracted away the React specifics. The only two user-facing dependancies we should be OK with are `php` and `node`, IMHO, even if we use the latest-and-shiny under the hood (well, `grunt` hasn't be new or shiny for a long time and all probably go away, which is a great example of why we should have our own façade in front of the JS hotnesses).
     1One forward-facing requirement I’d add is to not depend on `grunt`, `npm`, or `webpack` in the CLI tools or configuration of the new build system – the same way WordPress hasn't depended on any framework, even Gutenberg has abstracted away the React specifics. The only two user-facing dependancies we should be OK with are `php` and `node`, IMHO, even if we use the latest-and-shiny under the hood (well, `grunt` hasn't be new or shiny for a long time and will probably go away, which is a great example of why we should have our own façade in front of the JS hotnesses).