You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is for upgrading the Node version since 16 (current version) has reached the end of it’s security support period. Since we rely on WP and WC components we should probably follow along with the Gutenberg issue:
The first example blocks this extension to use v18 for now, and the second one may force it to downgrade to v16 in the future.
How to check
Since packages don't always accurately reflect the scope of Node.js support for children dependencies, confirming that these blocks have been removed usually requires actually upgrading the dependencies and testing the installation with Node.js v18 to see if it completes successfully.
Until then, another way to get a quick overview of package's Node.js support is npm view <packageName> engines, for example:
Details
This issue is for upgrading the Node version since 16 (current version) has reached the end of it’s security support period. Since we rely on WP and WC components we should probably follow along with the Gutenberg issue:
WordPress/gutenberg#48588
Their current plan is to jump to Node 20.
This issue will also be helpful to collect any blockers which might be preventing us from upgrading the Node version.
Is your feature request related to a problem?
Node 16 (current version) has reached the end of it’s [security support period]
Describe the solution you'd like
Update to Node 20
📌 Blockers to check
Why blocked
With the current dependency tree, there are some packages do not / will not support Node.js v20, for example:
@es-joy/[email protected]
, a child dependency of@wordpress/[email protected]
, doesn't support v18.@woocommerce/[email protected]
, but@woocommerce/[email protected]
(the current L-2 WC) only supports v16.The first example blocks this extension to use v18 for now, and the second one may force it to downgrade to v16 in the future.
How to check
Since packages don't always accurately reflect the scope of Node.js support for children dependencies, confirming that these blocks have been removed usually requires actually upgrading the dependencies and testing the installation with Node.js v18 to see if it completes successfully.
Until then, another way to get a quick overview of package's Node.js support is
npm view <packageName> engines
, for example:Acceptance criteria
The text was updated successfully, but these errors were encountered: