# faker-js/faker · RepoSense Release & Migration Intelligence

> fix(locale): exclude forbidden letter combinations from nl. Drop-in upgrade. Migration: None.

## Metadata
- **Repository URL**: https://github.com/faker-js/faker
- **Primary Package**: `@faker-js/faker` (NPM)
- **Categories**: `ECOSYSTEM`, `TESTING`
- **Latest Version**: `v10.6.0`
- **Semantic Status**: `COMPATIBLE`
- **Bundle Size Impact (unavailable)**: `Size Unavailable`
- **Atom Ingestion Feed**: https://github.com/faker-js/faker/releases.atom

## The Human Context (Plain-English Pitch)
@faker-js/faker is an open-source library and developer tool in the faker-js/faker ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.

## Stage 1 Executive Summary ([Core Change] + [Required Action] + [Migration Effort])
fix(locale): exclude forbidden letter combinations from nl. Drop-in upgrade. Migration: None.

## Breaking Changes & Required Actions
- fix(locale): exclude forbidden letter combinations from nl postcodes by @chatman-media in #3888
- feat(locale): add Norwegian (nb_NO) animal module by @arvindfroi in #3901
- feat(locale): add Norwegian (nb_NO) food module by @arvindfroi in #3900
- fix(locale): only generate valid French postal codes by @MahinAnowar in #3905

## Migration Snippet
```ts
npm install @faker-js/faker@10.6.0
```

## Ecosystem Compatibility Matrix & Graph Warnings
- **TypeScript 5.x** [`COMPATIBLE`]: Ships standard TypeScript declaration files without type regressions.

## Zero-Noise Release Timeline
- **v10.6.0** (2026-08-14) [COMPATIBLE]: fix(locale): exclude forbidden letter combinations from nl. Drop-in upgrade. Migration: None.

## Upgrade & Migration Q&A (GEO Direct Answers)
### Is faker-js/faker v10.6.0 safe to upgrade in production?
faker-js/faker v10.6.0 is classified as COMPATIBLE (MINOR release). fix(locale): exclude forbidden letter combinations from nl. Drop-in upgrade. Migration: None.

### What breaking changes or compatibility risks exist in faker-js/faker v10.6.0?
No breaking API changes or peer dependency conflicts are recorded for faker-js/faker v10.6.0 in the RepoSense compatibility graph.

### What is the bundle size impact of @faker-js/faker v10.6.0?
Measured bundle size telemetry is currently unavailable for @faker-js/faker v10.6.0; verify build output locally before deploying.

### How do I upgrade @faker-js/faker to v10.6.0?
Upgrade @faker-js/faker to v10.6.0 by running "npm install @faker-js/faker@10.6.0" and applying the migration steps: npm install @faker-js/faker@10.6.0
