On Sunday, November 20, 2016 at 5:06:26 PM UTC+1, Nicholas Zakas wrote: > > > We release eslint-config-eslint only periodically as we need it in other > projects. It's not really intended for others to use, though you are > certainly welcome to use it. However, we can't promise when exactly it will > be updated.
Sigh. Any workaround to use it (without copy and paste)? I tried a "github url" approach in package.json, but npm doesn't allow an url as subdir of the repo. (https://github.com/npm/npm/issues/2974) I thought to use it somehow referencing it directly from "node_modules" folder, but it is not distributed in npm package. Is feasible updating it every time eslint package is updated? Another approach is publishing and updating a new config (for instance, eslint-config-original), when the original one changes. Alternate solution. Feature request. What if we have something like "eslint:recommended" (tentative naming): extends: "eslint:default" I hope we get a right deal here. :) Cheers, Alberto -- 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.
