A linter for Polymer projects that catches errors before running code.
Polylint is a specialized linting tool for Polymer web component projects. It performs static analysis on Polymer code to identify errors, inconsistencies, and potential issues before the code is executed. The tool helps developers maintain code quality and catch problems early in the development process.
Polymer developers and teams building web applications with Polymer web components who want to improve code quality through static analysis.
Developers choose Polylint because it provides Polymer-specific linting that understands the framework's syntax and patterns, offers editor integrations for real-time feedback, and helps prevent runtime errors through early detection during development.
Lint polymer!
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Catches errors in Polymer code before execution, as stated in the README's tagline 'Catch errors in your polymer project before even running your code.'
Can lint entire projects with multiple HTML entry points, demonstrated by the usage example with inputs like index.html and cart.html.
Provides plugins for Atom and Sublime Text editors for inline linting, with specific installation steps outlined in the README.
Offers a CLI with configurable options for terminal-based linting, as shown in the usage example with --root and --input flags.
The README explicitly states it's deprecated and directs users to polymer-linter, meaning no bug fixes or updates are provided.
From the deprecation note, it's designed for older Polymer versions and lacks compatibility with Polymer 2.x or 3.x, forcing migration for newer projects.
Editor integrations are only for Atom and Sublime, which are less common today, and it lacks support for modern IDEs like VS Code or current build tools.