Publish 6.0.0 as `@faker-js/faker` about faker HOT 3 CLOSED

I've already acquired ownership -- see: #19

from faker.

Did we already claim the npm org?
If not, please do that immediately

https://www.npmjs.com/package/@faker-js/faker

Maybe we could also release a 5.5.3 🤔
That way the community can already just replace the dep to our package without any issues (except for no TS support 🤔)

from faker.

In a review of what was previously in the repo (but omitted from 5.5.3) and what will now be released with 6.0.0 is the new word API in the distributed faker.js in dist/faker.js and dist/faker.min.js.

word was (and continues to be) published in lib, so NodeJS users (and those browser users using a bundler) had access to word but unpkg users did not.

As a note, this means that these two file sizes have grown significantly:

A large portion of the filesize in the unminified files comes from the source maps.

I'm wondering two things:

1. Should no longer publish the unminified form in dist in order to save everyone's bandwidth costs.
2. How quickly (after 6.0.0) do we have to move to separately loadable locales and APIs to mitigate bandwidth issues.

from faker.