Javascript Chat Summary – July 17th

Below is a summary of the discussion from this week’s JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. chat (agendaSlack transcript).

Attending: @abdullahramzan@adamsilverstein@aduth@gziolo@herregroen@hypest, @andrei.lupu, @netweb@rheinardkorf, @tofumatt, @soen, @chopinbach, @nerrad, @youknowriad

Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.

Agenda Item: Versions of Node and NPM used in WordPress projects

Slack Conversation

This agenda item focused around discussing what versions of Node and NPM is used in WordPress projects and specifically within the context of what can be worked with within The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. build platform constraints.

The current request can be tracked here.


What? Who?
Request from systems making available node 10/npm 6.
This will be in use until October and at that point, the operating policy will be using the LTS version of Node plus whatever NPM ships with that version.
Update various configuration/settings files in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. and wordpress-develop: .nvmrc, package.json, engines (etc). @netweb

Agenda Item: Packages

Slack Conversation

Some new packages have been merged to Gutenberg (not published at time of meeting):

  • @wordpress/html-entities
  • @wordpress/viewport
  • @wordpress/compose
  • @wordpress/components
  • @wordpress/api-fetch

There was discussion around the publishing process and improving it which includes moving towards automating some of the publishing process (which includes adopting conventional commits).  

Further discussion on this topic can be tracked via this Github issue.


What? Who?
Continue to identify and work on improvements to the publishing process that get it to “automating as much as possible as soon as possible”.  

Agenda Item: New compose package

Slack Conversation

The idea is to define precisely what should and shouldn’t go in each package without ending up with a catch-all components package.  The result is:

  • element: just the base APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to build elements and components.
  • compose: a set of UIUI User interface-less higher-order components and functions that can be used to build other components.
  • components: A set of UI-related components and higher-order components. 

Longer term this can be seen as Pattern library for WordPress.

Roadmap for this package structure can be found here.

Agenda Item: Proposal to extract Gutenberg’s ESLint configuration to a new module

Slack Conversation

Reference: Github pull request for proposal

Discussion took place around whether the current proposal should be called a “WordPress Standard Configuration”.  There was opposition expressed to the PR in its current form.


What? Who?
Between now and next meeting there needs to be assembled a detailed set of divergences that need to be proposed for consideration.
Post published proposing changes outlined from the above discovery process to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. @aduth
Decision made on submitted proposal (involving wider WP team). 
This means no configuration will be published until this decision.