All,

Our UI building in packages/PRs uses npm v14, while the current LTS version is 
v18. However, since we use npm for only development and building the UI 
statically there are hopefully no concerns around security and support.

I've been using both v14 and v16 to build UI across different branches that 
haven't EOL'd. With npm v16 and ACS 4.18, I'm not able to npm install and npm 
run serve without the following:

export NODE_OPTIONS=--openssl-legacy-provider


npm also is trying to change the package-lock file with a new format, 
considering this should we consider moving to support the latest LTS (v18) or 
switch to another UI pkg building tool (such as yarn)? Thoughts?


Regards.

 

Reply via email to