Updating plugin editor to new node version

Hello @grace.hong , @sam.morgan

I encountered today quite some issues (to say the least) with node-14 upgraded plugins on production applications, whereas if executed from the test application of that plugin, everything was fine.

Let’s say one of my plugin user uses this node-14 version plugin (containing node-14 specific syntax) by upgrading from his application from the Plugin panel…is the node-14 upgraded plugin really running on node-14 ?

Just a wild guess here, but it looks like:

  • node-12 is still used on production clusters even though the plugin has been upgraded to node-14 from the plugin editor and published.
  • node-14 is used only when the node-14-upgraded plugin is executed from its test app - test clusters I guess.

So, it means that a fully-tested node14-upgraded-plugin with its test app (on test cluster) may fail on production applications.
Hence, all manually-upgraded the plugins to node-14 by plugin authors MUST still be backward compatible with node-12.

Do you confirm?

3 Likes