fix: allow version 10 of the babel-loader peer dependency

[cek-roadmunk-tempo]

Additional details

There is a dependency between babel-loader and @cypress/webpack-preprocessor. The max babel-loader version allowed is v9. This PR bumps the allowed version to v10.

Here are the breaking changes in babel-loader v10:

• bump node requirement to ^18.20.0 || ^20.10.0 || >=22.0.0 and webpack requirement to >= 5.61.0
• breaking: use output.hashFunction as loader cache hasher

As far as I can ascertain, this should have no negative effects on this package or cypress.

Steps to test

I used npm link to install the modified @cypress/webpack-preprocessor package into my own cypress project with babel-loader v10. I didn't encounter any issues.

How has the user experience changed?

No change.

PR Tasks

• [na] Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[CLAassistant]

All committers have signed the CLA.

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[cek-roadmunk-tempo]

I used the v9 babel-loader dependency update as a reference.

[AtofStryker]

Hi @cek-roadmunk-tempo. Thank you for opening a PR. This is currently a breaking change where this PR stands, but adding the code suggestion below would fix that. Would you also be able to update the babel-loader dependency in webpack-preprocessor if you have time just to help with test coverage?

[cek-roadmunk-tempo]

Would you also be able to update the babel-loader dependency in webpack-preprocessor if you have time just to help with test coverage?

I'll work on this next.

[cek-roadmunk-tempo]

Concerning the failed check, is there anything I should do?

[AtofStryker]

Concerning the failed check, is there anything I should do?

@cek-roadmunk-tempo I don't think so. It looks like build flake which sometimes happens with contributor PRs. If it continues to be a problem, I will investigate