Sheriff release v14
Sheriff, the ESLint sharable config, has exciting news to share!
With a complete rebranding, a restructured codebase, and exciting plans ahead, Sheriff is set to become an even more essential tool for ensuring code quality and consistency in projects.
Let's walkthrough the key changes of this release.
Restructured Codebase in a monorepo
The codebase has been restructured into a monorepo setup with Turborepo + pnpm workspaces, as it allows for the management of multiple related packages under a single repository, streamlining the development process and enabling better coordination between different parts of the project.
The documentation has been fully revamped, moving on from Gitbook to Docusaurus, a modern documentation framework.
Whether a newcomer or a seasoned user, the documentation is more accessible and easier to navigate, with a sidebar that allows for quick access to the different sections.
Also, a special Rules page was carefully crafted to let users explore in detail all the rules that Sheriff enables.
Visit the new docs at this link.
The beginning of a fresh era for Sheriff is marked by a new logo, that features the iconic ESLint logo and a shield.
A brand-new blog is now available, where I'll keep sharing updates on the projects as it grows along.
The focus remains on continuously improving the tool, making it more adaptable, and responding to the evolving needs of the development community.
Looking ahead, several exciting developments are in store:
- Astro Support: In the continuous effort to integrate more eslint-plugins into Sheriff, the next in line is eslint-plugin-astro.
- Searchbar: full-text search, powered by Algolia in the new docs.
- Ask AI: along with the new searchbar will come an "Ask AI bot" feature. Details on this one are still being worked on.
With this much-needed facelift, Sheriff is ready to keep growing. With a new documentation hub powered by Docusaurus, logo, and blog in place, Sheriff is set to provide an even more exceptional ESLint sharable config experience.
If you want to help feel free to propose new features, both for the config and the docs, or report any bug you might come across.
Stay tuned for updates and insights on the new blog!