NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev · #554 most downloaded on pub.dev
A package to help writing custom linters
Last release 1 years ago
09 Sep 2025
Release timing varies
gaps range from 9 days to 5 months
Nearly every release is documented
notes for 59 of the last 60 stable releases
1 version withdrawn
withdrawn after publishing
4 years old
75 releases · first in 2022
One column per quarter.
Fix custom_lint not working in the IDE
Add debugger and hot-reload support (Thanks to @TimWhiting)
exclude obtains from the analysis_options.yamldart analyze incorrectly failing due to showing the "plugin is starting" lint.Upgrade dependencies
Upgrade dependencies
Upgrade dependencies
Upgrade dependencies
Fix deprecation errors with analyzer
Lint fixes can now be used when placing the cursor on the last character of a lint
Nothing published for this version
Allow lints to emit fixes
Allow lints to emit fixes
Fix a bug where the custom_lint command line may not list all lints
Fix a bug where the custom_lint command line may not list all lints
feat!: getLints now is expected to return a Stream instead of Iterable
feat!: getLints now is expected to return a Stream<Lint> instead of Iterable<Lint>
fix: a bug where the lints shown by the IDE could get out of sync with the actual content of the file
Nothing published for this version
Fixed a bug where the command line could show IDE-only meant for debugging
PluginBase.getLints now receive a ResolvedUnitResult instead of a LibraryElement.
PluginBase.getLints now receive a ResolvedUnitResult instead of a LibraryElement.
Compilation errors are now visible within the pubspec.yaml of applications that are using the plugin.
Compilation errors are now visible within the pubspec.yaml of applications
that are using the plugin.
Plugins that are currently loading are now highlighted inside the pubspec.yaml
of applications that are using the plugin.
If a plugin throws when trying to analyze a Dart file, the IDE will now show the exception at the top of the analyzed file.
Compilation errors, exceptions and prints are now accessible within
a log file (custom_lint.log) inside applications using the plugin.
Initial release
Initial release
Your coding agent can read these notes before it upgrades. Set up the MCP server →