Re-Use the same faker imports for api-docs and locale-docs

[ST-DDT]

Clear and concise description of the problem

Currently, the api-code examples and browser console use one set of faker for execution, while the locale docs use a different one.
This causes additional delay on mobile, especially since the embedded 1MB download appears to be exempt from cache.

Suggested solution

Use the same download for both.

Alternative

Calculate the example values at docs build time, since they cannot be refreshed by the user.

Additional context

• docs: add a doc page for each locale #3654

[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