Shinigami

Yeah, we could export it, but we should then name it like `FakerDate` or something like this Currently it is an internal not exported type ... But when we do...

@JontyMC As a workaround, try `type FakerDate = typeof faker.date` for now

`FakerDate` feels like a wrapper around `Date` (the real js thingy), and IMO this is wrong / gives a wrong assumption to the user. `_Date` is currently just one if...

Accessing `@faker-js/faker/date` is not officially supported (at least not by design). It is nowhere documented and not intended to be used like this. If it would be official, it would...

Just to raise my voice because I suffer in silence: I would suggest to name it strategy instead of errorHandling

The current only way I could imagine of would be to create a `next` branch that between PRs and the main branch. But I'm not sure if we want the...

> another option could be to add `@since` tags to the documentation, then each method could be annotated in the docs with which version it was added > > [jsdoc.app/tags-since.html](https://jsdoc.app/tags-since.html)...

But then they would look where v7.4 is released, but there is no v7.4 release and they would ask us for that missing release So it would move the problem...

Current State 

> Amazing! thx :3 > Do we want to search for only the names or do we also want to search for some (hidden) aliases/tags? Not sure, I would start...