feat(locale): Add bn_BD locale

[AbrarShahriar]

Added Bengali locale.

Modified Modules:

• Date

[netlify]

✅ Deploy Preview for fakerjs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	55ae211
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/67d533dc0dbe3e000864e527
😎 Deploy Preview	https://deploy-preview-3439.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.97%. Comparing base (50b3241) to head (55ae211).
Report is 1 commits behind head on next.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #3439      +/-   ##
==========================================
- Coverage   99.97%   99.97%   -0.01%     
==========================================
  Files        2811     2817       +6     
  Lines      217414   217493      +79     
  Branches      951      951              
==========================================
+ Hits       217361   217438      +77     
- Misses         53       55       +2     

Files with missing lines	Coverage Δ
src/locale/bn_BD.ts	100.00% <100.00%> (ø)
src/locale/index.ts	100.00% <100.00%> (ø)
src/locales/bn_BD/date/index.ts	100.00% <100.00%> (ø)
src/locales/bn_BD/date/month.ts	100.00% <100.00%> (ø)
src/locales/bn_BD/date/weekday.ts	100.00% <100.00%> (ø)
src/locales/bn_BD/index.ts	100.00% <100.00%> (ø)
src/locales/bn_BD/metadata.ts	100.00% <100.00%> (ø)
src/locales/index.ts	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[matthewmayer]

In order to make it easier to review new locales, we generally ask for pull requests to contain a smaller number of files, and focus on a single module at a time.

Could I suggest you make a new pull request which just contains

• the Bengali metadata
• one simple locale data file (e.g. "date" or "animal")

Once that is approved you can follow up with additional PRs to add the remaining data.

Also we should decide if we want the locale code to be bn or bn_BD (Bangladesh) - since the phone numbers etc (and the cities?) are country-specific, it should probably be bn_BD.

[AbrarShahriar]

@matthewmayer Sure! I’ve updated the PR based on your feedback:

• Removed all modules except date.
• Renamed the locale code to bn_BD since phone formats and locations are Bangladesh-specific. Let me know if something else has been decided.
• Updated the metadata to reflect Bengali (Bangladesh).

[AbrarShahriar]

@matthewmayer Hey, made the changes you said. Although after running preflight, a few entries were added with the key bn_BD and I tried to manually fix them.

This PR might've become a little bit too messy for review. If you encounter any issues or suggest any changes, let me know. Also if this PR is becoming troublesome, I can open another PR with the changes you mentioned.

[matthewmayer]

It's fine. Let's keep it in one PR. We always squash-merge when approving so all the little tweaks don't appear in the main history.

I recommend looking at the files view on GitHub to check all changes for your PR. Then it's easier to see if there are any accidental changes that need reverting.

Thanks for your contributions!

[AbrarShahriar]

@matthewmayer I reverted the changes as you mentioned. Hopefully it should be okay now.

[xDivisionByZerox]

Thank you for your contribution and the great cooperation with matt ❤️
I'll leave the PR open for at least another 24 hours, so other team members have the chance of reviewing as well.

[Shinigami92]

LGTM (does not include a bitcoin miner 😜)

[AbrarShahriar]

@xDivisionByZerox Thank you, glad to be of some help<3

[AbrarShahriar]

@Shinigami92 Haha, relieved it passed the crypto-miner test! 😆

[matthewmayer]

@AbrarShahriar you can follow up with additional PRs for more modules now

For ease of review please make sure

• you branch from the current HEAD of the next branch each time
• you only propose data for one module, or a small group of related modules, at a time
• you list the source of the data e.g. if its your own research, or uses AI, or from any official published lists etc - so we can check for any copyright issues
• you sort all string arrays alphabetically (with a naive Unicode sort) - only certain modules require this but its good practice for all new modules

[AbrarShahriar]

@matthewmayer Thanks for the guidance!
I had a query. Do I create a new branch from the current HEAD of the next branch for each module update, or do I work on the current HEAD of the next branch directly?

[matthewmayer]

Suggest a new branch for each change based on the current HEAD of next.