Roadmap to Gremlins.js 2.0

[HALLERPierre]

Roadmap to Gremlins 2.0

Gremlins.js is now older than 6 years old and the last commit is 2 year old. We think it’s time to give some love to this useful and fun package !

That’s with this gold in mind that @zyhou and @HALLERPierre are the new maintainers of this project.

Our first goal is to give a new youth to gremlins.js. Say goodbye to callbacks hell and say hello to promises and async functions !

But we won’t stop here, here is the roadmap to Gremlins v2 :

• Conventional commit and changelog (#135)
• Update dependency
  • eslint/prettier (#134)
  • chance (#137)
  • babel (#137)
  • webpack (#137)
• Add unit and integration tests
  • setup travis and jest (#138)
  • write tests (#147, #145, #144)
• Improve build
  • cjs, esm, mjs (#139)
  • Polyfill (#139)
• Deploy and CI
  • Continuous Integration (#138)
  • Bookmarktlet (#141)
• Refacto
  • Use promises instead of callbacks (#132)
  • Refresh javascript style (es6) (#127)
  • Improve config injection (#142)
  • Improve custom species/mogwais/stategies creation (#142)
• Readme and Documentation
  • Update Readme (#146)
  • Expose Gremlins in console (like lodash/datefns) (#149)
  • Contribution (#152)
• Communication release
  • Issues grooming
  • New issue
  • Article on Marmelab blog (https://marmelab.com/blog/2020/06/02/gremlins-2.html)

This will lead to a deep transformation of the library.

Before releasing a stable version, we'll publish next releases. Development has already started and is visible on the next branch. We tag related pull request with the 2.0 milestone so you can track our progress.

Comments and contributing are welcome.

[HALLERPierre]

Here is the PR of the new version of Gremlins :
#157

[stof]

The changelog does not describe any BC break in 2.0. I find this confusing.

[Piedone]

Shouldn't this be closed? v2 has been out for a while.