Updates few project dependencies

[AdiAkhileshSingh15]

Changes Summary

This PR aims to update he existing dependencies to the latest LTS (Long Term Support) version.

The following dependencies have been updated:

devDependencies:

1. @babel/preset-env: Updated to version ^7.24.0
2. chalk: Updated to version ^4.1.2
3. css-loader: Updated to version ^6.10.0
4. electron: Updated to version ^29.1.1
5. electron-builder: Updated to version ^24.13.3
6. fbjs-scripts: Updated to version ^3.0.1
7. husky: Updated to version ^9.0.11
8. lint-staged: Updated to version ^15.2.2
9. react-test-renderer: Updated to version ^18.2.0
10. rimraf: Updated to version ^5.0.5
11. sass-loader: Updated to version ^14.1.1
12. sinon: Updated to version ^17.0.1
13. style-loader: Updated to version ^2.0.0
14. stylelint: Updated to version ^16.2.1
15. stylelint-config-prettier: Updated to version ^9.0.5
16. stylelint-config-standard: Updated to version ^36.0.0
17. testcafe-react-selectors: Updated to version ^5.0.3

dependencies:

1. @mui/lab: Updated to version ^5.0.0-alpha.167
2. github-markdown-css: Updated to version ^5.5.1
3. jest-extended: Updated to version 4.0.2

These tasks also include replacing the @babel/plugin-proposal-private-property-in-object with plugin-transform-private-property-in-object, as the npm suggests that @babel/plugin-proposal-private-property-in-object is deprecated. source.

All the dependencies are updated to their latest LTS version, except for chalk.
As chalk LTS version v5 was giving some build and dev errors due to the way imports were being made in the module.
"IMPORTANT: Chalk 5 is ESM. If you want to use Chalk with TypeScript or a build tool, you will probably want to use Chalk 4 for now."
I'd recommend you to go through this discussion. Pure ESM
Though, I don't think keeping it to an old yet newer version is helpful in long-run. It would require us to move towards dynamic imports for ESM version.

Also, one small update in github-markdown-css requires us to specify import of light scheme of styling unlike the previous version. Actually, I came to know that it reads the color-scheme of the app or the specific component, I tried to set the color scheme that way, but it didn't help, so, specifying the module import came in pretty useful.

Related Issue

Fixes: #171

Testing:

After updating dependencies, ran different checks using these commands locally to ensure functionality remains intact.
Use commands:

• yarn test - all tests passed
• yarn dev - no UI fails detected
• yarn build - no build fails detected
• yarn dev - no new consol errors detected for any dependencies

Reviewer(s)

@lrasmus

[Abhijay007]

Looks good to me! 👍. One more thing @AdiAkhileshSingh15, could you please squash these commits into one?

[AdiAkhileshSingh15]

Yeah sure! @Abhijay007

[AdiAkhileshSingh15]

@Abhijay007 Can I take up some more dependency updates in this branch or do I need to get these merged to master first?
I'll ensure to squash the upcoming commits into one while I do so.

[Abhijay007]

@Abhijay007 Can I take up some more dependency updates in this branch or do I need to get these merged to master first? I'll ensure to squash the upcoming commits into one while I do so.

sure @AdiAkhileshSingh15 you can add more dependencies updates in this branch, just update that in both the issue list and PR description.

[AdiAkhileshSingh15]

Ohk sure! @Abhijay007

[AdiAkhileshSingh15]

In these changes, I couldn't update style-loader to v3, max it could have been updated to without breaking the dev was ^2.0.0. Some solutions on the web suggested to not use style-loader alongwith css-loader. Removing it didn't seem feasible so I updated it till v2, which kinda seems fine knowing that style-loader comes to use only in dev.

Here is the error message attached.
It seems to have something to do with react-hot-loader, which I didn't find anything useful about anywhere, also, updating it doesn't help.

[AdiAkhileshSingh15]

Changes made with my last commit to this branch:

devDependencies:

1. sass-loader: Updated to version ^14.1.1
2. sinon: Updated to version ^17.0.1
3. style-loader: Updated to version ^2.0.0
4. stylelint: Updated to version ^16.2.1
5. stylelint-config-prettier: Updated to version ^9.0.5
6. stylelint-config-standard: Updated to version ^36.0.0
7. testcafe-react-selectors: Updated to version ^5.0.3

dependencies:

1. jest-extended: Updated to version 4.0.2

[AdiAkhileshSingh15]

Updating stylelint threw a console error, Module build failed: Error: ENOENT: no such file or directory which didn't affect the overall working of the application UI, neither did it face any build or test errors.
This error came for some unified pkg, as it looked for a is-plain-obj folder, which was replaced by is-buffer folder in the node modules, most sources on the web suggested to reinstall the node modules or ignore this error.

[Abhijay007]

Updating stylelint threw a console error, Module build failed: Error: ENOENT: no such file or directory which didn't affect the overall working of the application UI, neither did it face any build or test errors. This error came for some unified pkg, as it looked for a is-plain-obj folder, which was replaced by is-buffer folder in the node modules, most sources on the web suggested to reinstall the node modules or ignore this error.

@AdiAkhileshSingh15, thanks for looking into this but could you please try reinstalling the 'node modules' as the sources suggest? If errors persist afterward, it's better to revert this change. Although it may not directly impact the high-level functionality, it could be causing some hidden errors or issues.

[AdiAkhileshSingh15]

Reinstalling node modules alongwith restarting dev server cleaned the console 👍🏻 No more such Module build failed: Error: ENOENT: no such file or directory errors.

[lrasmus]

Sorry for the delays, thank you so much @AdiAkhileshSingh15 for the changes, and @Abhijay007 for keeping this going while I was away!