Hi,
that would be a great feature for eslint. We have already implemented some
framework specific rules which we want to publish and share.
Ideally we'd like to be able to have rules packaged and shared via npm like
> any other package. The structure I'm thinking of is:
>
> * lib/
> * rules/
> * (rules files)
> * tests/
> * lib/
> * rules/
> * (test files)
>
Do you really want to include the tests in a packaged rules bundle?
Normally tests are excluded in a npm package by adding the folder to
.npmignore.
I suggest something like this:
* lib/ (or any other folder, this would be ignored by eslint anyway)
* (package specific libs/helpers)
* rules/
* (rules files)
Then, we could specify to load them in a config file as:
>
> {
> rulesets: [ "npm-package-name", "./path/to/package" ]
> }
>
This could also be helpful for grouping the core rules (as discussed in
eslint#692).
--
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.
