refactor(helpers)!: remove v8 deprecated unique

[Shinigami92]

extracted from #2608

• refactor!: remove v8 deprecations #2608

referencing #1785

• Deprecate helpers.unique for removal #1785

should be merged before starting #2335

• Can add sideEffects: false to package.json #2335

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.55%. Comparing base (fd05126) to head (ef40320).

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2661      +/-   ##
==========================================
- Coverage   99.55%   99.55%   -0.01%     
==========================================
  Files        2817     2816       -1     
  Lines      251188   250918     -270     
  Branches     1117      707     -410     
==========================================
- Hits       250074   249805     -269     
+ Misses       1114     1084      -30     
- Partials        0       29      +29     

Files	Coverage Δ
src/modules/helpers/index.ts	98.82% <ø> (-0.10%)	⬇️

... and 30 files with indirect coverage changes

[ST-DDT]

As mentioned earlier. I don't think we should remove unique from faker as it is a very useful feature when generating test data.
I would like to check with the rest of the team and to a certain extend the community, whether we should remove it or replace it.

EDIT: Reason: #2667 in combination with #2664 will likely invalidate the circumstances that the initial decision was made upon.

Please vote this comment with

• 👍 for removal of unique and
• 👎 for retaining unique, although with a different implementation and interface.

[matthewmayer]

What about the possibility of taking an external replacement like https://www.npmjs.com/package/enforce-unique and moving it within the faker-js org, but as a separate package/repo?

[Shinigami92]

As mentioned earlier. I don't think we should remove unique from faker as it is a very useful feature when generating test data.

I would like to check with the rest of the team and to a certain extend the community, whether we should remove it or replace it.

Please vote this comment with

• 👍 for removal of unique and

• 👎 for retaining unique, although with a different implementation and interface.

I need to say that I 100% dislike to bring up a long discussion we already had and even written down in our internal notes. As Matthew already wrote: there is another package that does the same if not better.
And for all the reasons: please lock back in history notes. Period.

[matthewmayer]

Let's just make sure we have very good documentation explaining how to migrate from using the existing method to a third-party package.

[matthewmayer]

i went ahead and added some documentation and suggested alternatives direct on this branch. Feedback welcome.

[Shinigami92]

Thank you @matthewmayer
I rebased it, fixed a conflict and fixed some minor typos

LGTM 👍

[ST-DDT]

Please dont rebase unless necessary as it makes reviews harder.

[matthewmayer]

This will also need a migration guide snippet. Hopefully it can be quite short now and just link to the unique guide page.

[Shinigami92]

This will also need a migration guide snippet. Hopefully it can be quite short now and just link to the unique guide page.

added

[MansurAliKoroglu]

I published a new version of enforce-unique. Now it supports exclude.

[ST-DDT]

Approved as per old team decision so it's no longer hard blocked, but I still think it's wrong.

[Shinigami92]

Approved as per old team decision so it's no longer hard blocked, but I still think it's wrong.

I owe you a favor 👍