Hello,
A few days ago, I received an issue on @luciferreeves/blaver to merge the project with this repo and maintain this project instead. Now, I'm not going to try and read the tea leaves and figure out what the future looks like. The question for me was, "Do I maintain the repo alone or move to a more community based approach?" I thought the answer was obvious and that I can maintain blaver, but now I'm convinced of the opposite.
I pondered over the question for a few days and I thought, its much easier to contribute to a public repository rather than a repo that I handle myself. I would continue to improve faker.js but I think it's much better if I do this here.
So, I would like to retire/archive the repo and update the readme of the project once I have a confirmation here and I would deprecate the package on NPM, and link to release of faker-js/faker.
I also registered a domain (blaver.dev), which I can point to fakerjs.dev, if you guys want that. Let me know what you think.
Hello,
A few days ago, I received an issue on
@luciferreeves/blaverto merge the project with this repo and maintain this project instead. Now, I'm not going to try and read the tea leaves and figure out what the future looks like. The question for me was, "Do I maintain the repo alone or move to a more community based approach?" I thought the answer was obvious and that I can maintainblaver, but now I'm convinced of the opposite.I pondered over the question for a few days and I thought, its much easier to contribute to a public repository rather than a repo that I handle myself. I would continue to improve faker.js but I think it's much better if I do this here.
So, I would like to retire/archive the repo and update the readme of the project once I have a confirmation here and I would deprecate the package on NPM, and link to release of
faker-js/faker.I also registered a domain (blaver.dev), which I can point to fakerjs.dev, if you guys want that. Let me know what you think.