Depend directly on eslint-plugin-standard and eslint-plugin-promise about eslint-config-standard HOT 7 CLOSED

Hi Max 👋 long time no see 😄

I believe that the reason for this is so that we can bump the version of eslint-plugin-standard and eslint-plugin-promise in standard without having to cut a new release of eslint-config-standard. I have also noticed this though and it might be a good idea to revisit this and weigh the pros and cons...

paging @feross :)

from eslint-config-standard.

I would love to make this change, but ESLint would need to support it directly. See issue here: eslint/eslint#3458

We could just add them as dependencies, but then you'd be relying on the npm3 flattening behavior that puts all packages in the top-level to make the plugin "findable" by eslint, which only looks for plugins in the top-level node_modules folder. If flattening didn't happen for a plugin for whatever reason (maybe another package somehow depending on the same plugin), then you'd be missing a dependency. Also, this wouldn't work at all for npm2 users.

from eslint-config-standard.

Hi Max 👋 long time no see 😄

Indeed, 😸, you show up like the old man in a box*.

I would love to make this change, but ESLint would need to support it directly. See issue here: eslint/eslint#3458
There seems to have been some moment there fairly recently, e.g. last december, and they are looking for a volunteer to switch to plugin shipping configs, rather then a config shipping plugins.

Would you mind trying it out? (I'm not familiar enough with how to do that I'm afraid)

*it's a Swedish thing, don't worry about it 😉

from eslint-config-standard.

Reopen?

from eslint-config-standard.

#91

from eslint-config-standard.

It looks like eslint/eslint#3458 is still unresolved. Has something changed?

from eslint-config-standard.

Nah. I didn't realize this is still an issue. I thought it would have been solved by npm by now. I'm following that issue.

from eslint-config-standard.