chore(deps): migrate to community @faker-js/faker

[MikeMcC399]

• Closes Migrate faker to supported version #30096

Additional details

• The npm module faker is currently listed as deprecated on Dependency Dashboard #3777

The deprecated npm module [email protected] is migrated to the identical (non-deprecated) community version @faker-js/[email protected]. See note in https://v6.fakerjs.dev/migration-guide-v5/

In addition to releasing all future versions under the @faker-js/faker package namespace, we have also provided all historical versions of Faker.

For background information read also I heard something happened. What's the TLDR?.

Steps to test

git clean -xfd
yarn
yarn workspace @packages/frontend-shared cypress:run:ct
yarn workspace @packages/frontend-shared check-ts
yarn workspace @packages/app check-ts

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?

[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.

[jennifer-shehane]

@MikeMcC399 Great! I'll kick off the tests.

[jennifer-shehane]

@MikeMcC399 Some relevant failures here: https://app.circleci.com/pipelines/github/cypress-io/cypress/63678/workflows/0390e57b-20a3-4945-827b-8fc6d4c5bf44/jobs/2640546/tests

[MikeMcC399]

@jennifer-shehane

Thanks for picking out the failures!

I reverted the tree-shaking syntax for importing faker which it seems is only good for @faker-js/faker@6 and not for the legacy @faker-js/[email protected] version.

The following tests all pass when run locally:

yarn workspace @packages/frontend-shared cypress:run:ct
yarn workspace @packages/frontend-shared cypress:run:ct --browser chrome
yarn workspace @packages/frontend-shared check-ts
yarn workspace @packages/app check-ts

[cypress-bot]

Released in 13.14.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.14.0, please open a new issue.