Resolve npm dependency issues in edx-platform

[ghassanmas]

The edx-platform has conflict in package dependency. This can help to resolve since various process or scripts starts by running npm install in the root of edx-platform which might take time even if node_modules have been already installed. since npm install runs preinstall cycle anyway REF

This issue might not too related to FEWG. however, it might be helpful to post here since it's related to FEWG type of expertise.

1- edx/edx-proctoring

MFE-Platform is edx/[email protected] while edx-proctoring-proctortrack is using edx/[email protected] [REF|https://github.com/anupdhabarde/edx-proctoring-proctortrack/blob/d717f3b7e1d5aec6290d7dd08646cba8c6af3499/package.json#L26].
Note: I am not sure about how edx-proctoring-proctortrack is intended to be installed, the link source returns the master branch here

2- selenium-webdriver

There multiple pacakges in dev depedency that uses the selenium-webdriver, however they conflict with each other, for example, karma-selenium-webdriver-launcher is using [email protected] REF however the platform it self is using [email protected] REF

Other Relevant Links

• Incrementally upgrade edx-platform NPM dependencies #105 (comment)
• Start deprecation of edx-ui-toolkit and ux-pattern-library edx/edx-arch-experiments#262 (comment)
• Cleanup that got reverted that might need to be put back on master: Revert "feat: Account and profile MFE legacy removal - redeployment " edx-platform#33542
• Upgrade Node JS from 16 to 20 edx-platform#31937 (comment)

[mamankhan99]

[email protected] is the latest version that is using [email protected] so an update is not possible here. I believe it isn't breaking anything at the moment and we can eventually exclude these packages from the project when we will break it down into more MFEs till then we can keep it.

[arbrandes]

@abdullahwaheed, @ishahroz: is this related to the Karma vs Jest conversation we had today? Is there another issue that tracks that?

[abdullahwaheed]

yes this issue is covered in #105 as well

[kdmccormick]

Some vague questions:

1. why is something installing selenium?
2. why is edx-proctoring or edx-proctoring-proctortrack installing into edx-platform as a node package, given that (I believe) it's been fully replatformed into an MFE?

[feanil]

The proctoring issue has been resolved here: openedx/edx-platform#34874

[feanil]

npm install now works cleanly so I'm gonna close this for now.