Andrew Ackerman

I've pushed a branch on a fork with my tentative solution: https://github.com/Abion47/faker/tree/%40fix/helper-fake-instance-access

> Alternative solution: > > * [Proposal: Replace internal fake patterns with a resolver function #3176](https://github.com/faker-js/faker/issues/3176) > > Instead of expanding the `fake` method to match `eval`, it might be...

@ST-DDT `fake` only producing strings* makes it all the more important for it to be able to mutate the results from `fakeEval` for when the raw output is something that...

@ST-DDT That was another thing that seems confusing to me. The only real difference between `fake` and `mustache` seems like `fake` can parse more advanced fields within the tags whereas...

Something I discovered while writing the tests is that I intended to base the tests on the `TypedArray`/`Uint8` tests, but those tests don't appear to have been written yet. Furthermore,...

Including Marak on the documentation for the new project is nothing more than a technical legal requirement and a professional courtesy. They lost the moral right of attribution when they...

@tonyqus It's not like he had an accident or made a mistake. He very deliberately broke both faker.js and colors.js knowing full well that it would crash, as a low...

@tonyqus As you know, `faker.js` got forked and now basically has new owners and maintainers. However, `colors.js` hasn't been forked with new owners because there's not really any reason to....

@subzero911 Use "Fix All Imports".

The existing unit tests should already cover this use case, and as far as I can tell, they are working as expected. Did you have a specific example that wasn't...