Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@faker-js/faker instead of faker #21

Open
aufdenpunkt opened this issue Aug 16, 2022 · 1 comment
Open

@faker-js/faker instead of faker #21

aufdenpunkt opened this issue Aug 16, 2022 · 1 comment

Comments

@aufdenpunkt
Copy link

Hi,

first I wanted to say thanks, for this awesome package.

Would it be possible to use @faker-js/faker (https://www.npmjs.com/package/@faker-js/faker) instead of faker?

I have done this locally by overwriting the faker package in my package.json with:

"faker": "npm:@faker-js/faker@latest"

The only things that I had to change in your package was using the dependency @faker-js/faker and adjusting the import from:

import faker from 'faker';

to

import { faker } from '@faker-js/faker';

Would be really great as the @faker-js/faker package has a lot of new generator functions.

Thanks and best,
Chris

@devcauldron
Copy link

@lykmapipo any word on this? The original 'faker' npm module has been completely wiped by the maintainer. Check the Github repo is now missing and the npm page has empty README so the maintainer had to go out of his way to publish an empty version. @faker-js/faker has now replaced it and is community maintained. Here is the website at fakerjs.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants