Describe the bug
Currently, v6.0.0-alpha.3 is published on npm under the latest tag. I think doing npm i @faker-js/faker should install the latest stable, not the latest alpha. Therefore, I'd suggest publishing v6.0.0-alpha.3 under the alpha tag (npm publish --tag alpha), and publishing a v5.5.4 (exact content of v5.5.3) under the latest tag.
Reproduction
Run npm i @faker-js/faker, it installs the latest alpha instead of the latest stable.
Additional Info
Note that maybe there's a valid reason to do so, I might be missing context here, since the library situation was/is quite complicated. 😉
Describe the bug
Currently, v6.0.0-alpha.3 is published on npm under the
latesttag. I think doingnpm i @faker-js/fakershould install the latest stable, not the latest alpha. Therefore, I'd suggest publishingv6.0.0-alpha.3under thealphatag (npm publish --tag alpha), and publishing av5.5.4(exact content of v5.5.3) under thelatesttag.Reproduction
Run
npm i @faker-js/faker, it installs the latest alpha instead of the latest stable.Additional Info
Note that maybe there's a valid reason to do so, I might be missing context here, since the library situation was/is quite complicated. 😉