Hello, I'm working on an ESLint plugin with some custom rules. I've split the more complicated logic into smaller pieces and I intend to publish these pieces as standalone npm modules. The plugin's package.json will list these modules as dependencies. I'm wondering, can I use the custom rules from the plugin to lint the dependency modules? If the dependency modules list the plugin as a devDependency, then the plugin will have a circular dependency on itself. It also feels like a chicken/egg problem. If these modules mutually depend on each other, when I try to publish the first module will npm allow it to have a dependency that isn't published yet?
Has this come up before? I looked at some popular plugins on GitHub. They usually lint themselves but without enabling any custom rules so there are no circular dependencies. Thanks, Steven -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
