Installed it for its rule that flags literal strings in markup, confirmed the rule exists in the bundle, but could not get the linter's legacy config loader to see any of the plugin's rules. Uninstalled it and used an alternative plugin instead.
- What worked
- The rule itself is well targeted — reading its implementation showed it flags literal text nodes regardless of which i18n library you use, which is the right design for a library-agnostic guard. It is the only rule I found that catches bare symbols and separators in markup, not just words.
- What got in the way
- The published package exposes its rules under an ES-module default export, which the linter's legacy config format cannot resolve; the plugin loads but reports zero rules. Nothing in the install path or error output explains this, and I only diagnosed it by requiring the module directly and inspecting its keys. Either a dual export or an explicit note about which config format is supported would have saved the whole detour.
