Faker support for Node v25.8

[mtsmel]

Clear and concise description of the problem

Getting and error with faker 10.3.0 when using Node v25.8....

Error: Package subpath './.' is not defined by "exports" in ...\node_modules@faker-js\faker\package.json

Suggested solution

Upgrade code to support Node v.25.8

Alternative

No response

Additional context

No response

[github-actions]

Thank you for your feature proposal.

We marked it as "waiting for user interest" for now to gather some feedback from our community:

• If you would like to see this feature be implemented, please react to the description with an up-vote (:+1:).
• If you have a suggestion or want to point out some special cases that need to be considered, please leave a comment, so we are aware about them.

We would also like to hear about other community members' use cases for the feature to give us a better understanding of their potential implicit or explicit requirements.

We will start the implementation based on:

• the number of votes ( 👍 ) and comments
• the relevance for the ecosystem
• availability of alternatives and workarounds
• and the complexity of the requested feature

We do this because:

• There are plenty of languages/countries out there and we would like to ensure that every method can cover all or almost all of them.
• Every feature we add to faker has "costs" associated to it:
  • initial costs: design, implementation, reviews, documentation
  • running costs: awareness of the feature itself, more complex module structure, increased bundle size, more work during refactors

---

View more issues which are waiting for user interest

[xDivisionByZerox]

I can confirm this bug inside our palyground. Tested on:

System:
    OS: Linux 6.6 Alpine Linux
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700KF
    Memory: 14.07 GB / 15.51 GB
    Container: Yes
    Shell: Unknown - /bin/sh
Binaries:
    Node: 25.8.1 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 11.11.0 - /usr/local/bin/npm

---

I'll look into this.

Actually, my local setup still had an overwrite from my last local test. So I still had a broken Faker package "installed". My bad.

[xDivisionByZerox]

Ignore my previous comment. When I try to use Faker version 10.3.0 (or 10.4.0) with Node v25.8.1 I can successfully run all our tests in faker-js/playground.

@mtsmel can you provide a minimal reproduction that shows the undesired behavior?

[mtsmel]

I’m on 10.1… let me update to 10.4 and try to execute…. Thx

…

Sent from my iPhone On Mar 24, 2026, at 4:48 PM, DivisionByZero ***@***.***> wrote:  [https://avatars.githubusercontent.com/u/77127505?s=20&v=4]xDivisionByZerox left a comment (faker-js/faker#3769)<#3769 (comment)> Ignore my previous comment. When I try to use Faker version 10.3.0 (or 10.4.0) with Node v25.8.1 I can successfully run all our tests in faker-js/playground<https://github.com/faker-js/playground>. @mtsmel<https://github.com/mtsmel> can you provide a minimal reproduction that shows the undesired behavior? — Reply to this email directly, view it on GitHub<#3769?email_source=notifications&email_token=AKWK23VWQYVTK6MZUBR5RLT4SL7D3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJSGE3DEMZUGA22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4121623405>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKWK23SZYBQJU26ZWCPY4434SL7D3AVCNFSM6AAAAACW54K5V6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMRRGYZDGNBQGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>