this is looking less and less possible the more i look at it.

apparently eslint resolves plugins from the cwd which means we'd have to require the consumer to install both as peers anyway to be safe. if we tried to rely on the dependency here, it could be nested and will fail to resolve at lint time.

kinda sucks, guess i might throw this away after all

thoughts @stramel?

I think using the shared config that extends the recommended WC plugin config is the right route. Just need to inform the consumers they need to also install WC plugin as well. Eslint documents that under their shared config section.

im gonna abandon this until eslint flat configs are more of a thing (less experimental), then we can have a much simpler hierarchy (since it allows chaining plugins like this).