Static JS load issue- after Node version upgrade from 14.x.x to 16.x.x to resolve @ckeditor/[email protected] library node incompatible issue

[devendra-tarento]

We were using SunbirdEd release-5.1.1 from last couple of month and from last week we started facing below issue when doing client app package installation.

13:56:50 warning [email protected]: We have news to share - Protractor is deprecated and will reach end-of-life by Summer 2023. To learn more and find out about other options please refer to this post on the Angular blog. Thank you for using and contributing to Protractor. https://goo.gle/state-of-e2e-in-angular
13:56:50 warning protractor > webdriver-manager > [email protected]: request has been deprecated, see https://github.com/request/request/issues/314213:56:50 warning [email protected]: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information. 
13:56:51 [3/5] Fetching packages... 1
3:56:55 error @ckeditor/[email protected]: The engine "node" is incompatible with this module. Expected version ">=16.0.0". Got "14.19.0" 
13:56:55 error Found incompatible module. 
13:56:55 info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. 
13:56:55 Client and Server Build complete Took 127 seconds to complete. 
13:56:55 starting docker build 
13:57:05 Sending build context to Docker daemon 470.4MB

Looking at the error it seems that one of the external library @ckeditor/ckeditor5-core used in our editor got recent update with minimum node version 16.x.x.

To fix this we upgraded the node version to 16.x.x and it worked well in local system but when we upgraded the node version to 16.x.x in our Dev server. We started facing 504 gateway timeout issue for some of the static files (js, svg, etc) randomly.

Is anyone else facing the same issue ?
Is upgrading to node 16.x.x risk as of now ?
What could be the possible solution to this ?

Note: I also checked latest code base of release-5.2.0 of SunbirdEd and found that build.sh, Dockerfile and Dockerfile.Build still have node version 14.19.0 . Does it mean SunbirdEd still using node 14.x.x in their servers.

@vinukumar-vs @rajeevsathish @Krishnaj20

[vinukumar-vs]

@rajeevsathish we also faced the same issue recently while upgrading of Sunbird-ED portal to Angular 14 right?

The reason because, any one of the NPM package(^ - minor updates) is not supported with node v14.
https://github.com/Sunbird-Knowlg/sunbird-collection-editor/blob/main/package.json

"@project-sunbird/ckeditor-build-classic": "^4.1.3",

This is pointing to Sunbird forked Ckeditor repo
https://github.com/Sunbird-Ed/ckeditor5/blob/master/package.json

In the above repo all the NPM libraries are added using "^". Hence there can be an issue with any one of the library minor updates.

@sajeshkayyath @pallakartheekreddy @HarishGangula @rajeevsathish

[vinukumar-vs]

@devendra-tarento Can you create new discuss this in inQuiry to discuss this. This is related to collection/question-set editor issue.

@sajeshkayyath @Krishnaj20 @rajeevsathish

[devendra-tarento]

@vinukumar-vs Thanks for the explanation. I will create a new discussion in inQuiry .

[sajeshkayyath]

@devendra-tarento - an update has been posted here
https://github.com/orgs/Sunbird-inQuiry/discussions/73#discussioncomment-5720128

@vinukumar-vs @rajeevsathish @Krishnaj20