[fflorent]

Bumps the dependencies, especially selenium.

This action has been made by Copilot.

What I have done:

1. Reverted any source code modification (the one proposed were useless);
2. package-lock.json and yarn.lock files have been generated myself.
3. Run locally npm run build, yarn build, yarn test and npm test, everything works as expected (using node v24.14.0)
4. Also I ran npm audit fix to fix some vulnerabilities in dependencies, and removed yarn.lock file to regenerate it from package-lock.json using yarn import (so yarn.lock also benefits from the changes brought by npm audit fix)

[fflorent]

I wonder if for mocha, chai-as-promised and chai it would not be possible and better to make them peer dependencies (but it might have some drawbacks too, not 100% sure of myself)

[dsagal]

Thank you @fflorent! How do you feel about removing yarn.lock and dropping all references to yarn? All commands use npm, and npm seems sufficient for this repo. No need to maintain two approaches.

Also, would you like to try upgrading tslint to latest? It seems responsible for some npm audit warnings.

For package-lock, it may be good to delete it and recreate by reinstalling from scratch. I suspect there will be no difference to build/lint/test (and package-lock does not affect packages that depend on mocha-webdriver), and there is a chance it would fix some other npm audit warnings.

[fflorent]

@dsagal Makes sense, thanks!

Also, would you like to try upgrading tslint to latest? It seems responsible for some npm audit warnings.

tslint is deprecated in favor of eslint: https://www.npmjs.com/package/tslint

I take a look at this package to see whether I can migrate easily: https://www.npmjs.com/package/tslint-to-eslint-config

[dsagal]

Yeah, I didn't want to create more work for you. Feel free to ruthlessly upgrade to the same eslint config as grist-core (or keep as tslint). There is almost never any changes to this package, so there is not going to be much debate on code styles.

[fflorent]

@dsagal Done. Also there seem to remain some npm audit warnings that will be fixed with the next version of mocha:
mochajs/mocha#5589

[dsagal]

Thank you!

[dsagal]

Actually version 0.3.4 was already the published one, but not merged into master. I bumped this to 0.3.5 and published to npm.