Re: [DISCUSS] Fixing npm version for building UI

[Daan Hoogland <da...@gmail.com>]

Hey Rohit,
guess this is not a hot topic, but i'm +1 on this. with 4.18 out I think
now is a good time.

On Thu, Aug 10, 2023 at 10:53 AM Rohit Yadav <ro...@shapeblue.com>
wrote:

> 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.
>
>
>
>

-- 
Daan

Re: [DISCUSS] Fixing npm version for building UI

[Guto Veronezi <gu...@apache.org>]

Hello guys,

I think Rohit meant to upgrade the Node version to v18, as NPM is only 
the package manager and its latest release is 10.0.

Currently, we do not enforce either Node or NPM version in the building; 
therefore, one can use newer Node versions rather than v14. The problem 
faced by Rohit is a known issue caused by an incompatibility of Webpack 
4+ with OpenSSL 3.0[1]; enforcing Node v18 will not fix the problem, and 
neither will moving to another building tool.

Best regards,
Daniel Salvador (gutoveronezi)

[1] https://github.com/webpack/webpack/issues/14532

On 9/18/23 11:13, Daan Hoogland wrote:
> Hey Rohit,
> guess this is not a hot topic, but i'm +1 on this. with 4.18 out I think
> now is a good time.
>
> On Thu, Aug 10, 2023 at 10:53 AM Rohit Yadav <ro...@shapeblue.com>
> wrote:
>
>> 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.
>>
>>
>>
>>