chore(deps): bump @faker-js/faker from 9.9.0 to 10.4.0 - #314
Merged
Conversation
No code migration needed: the project only uses faker.system.*, faker.date.past/recent, faker.string.uuid, faker.number.int and faker.helpers.arrayElement — none of which changed in v10. The removed v9 deprecations (address.*->location.*, name.*->person.*) and the word-module 'fail' strategy change are unused here. All imports are already ESM named imports (v10 is ESM-only) and the project runs Vitest, not Jest. Node 22 satisfies v10's engines (^22.13.0). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (80.40% Estimated after merge)
lisaparma
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@faker-js/fakerChangelog
v10.0.0New & Noteworthy
What's Changed
Full Changelog: faker-js/faker@v9.9.0...v10.0.0
v10.0.0-beta.0What's Changed
Full Changelog: faker-js/faker@v9.9.0...v10.0.0-beta.0
v10.1.0What's Changed
New Contributors
Full Changelog: faker-js/faker@v10.0.0...v10.1.0
v10.2.0What's Changed
New Contributors
Full Changelog: faker-js/faker@v10.1.0...v10.2.0
v10.3.0What's Changed
sexTypecan return'generic'by @ST-DDT in feat(person):sexTypecan return'generic'faker-js/faker#3259New Contributors
Full Changelog: faker-js/faker@v10.2.0...v10.3.0
v10.4.0What's Changed
New Contributors
Full Changelog: faker-js/faker@v10.3.0...v10.4.0
Code changes
Nessuna modifica al codice. Il progetto usa solo
faker.system.*(fileName({ extensionCount }),fileExt,mimeType,commonFileName),faker.date.past/recent,faker.string.uuid,faker.number.int,faker.helpers.arrayElement— nessuna di queste API è cambiata in v10.Breaking change v10 verificate come non impattanti:
import { faker } from '@faker-js/faker'e il progetto usa Vitest (non Jest).address.*→location.*,name.*→person.*): non usate nel repo.wordmodule error strategy → 'fail':faker.word.*non è usato.^20.19 || ^22.13 || >=24): il progetto è su Node 22 ✅.Fonte migrazione: context7
/faker-js/faker— guida upgrading v10.Verification
Note
date-fns@^4.1.0(richiesto da@zextras/carbonio-design-system) non correlato a questo bump.