Lodash eslint rules for better tree-shaking

[darrenjaneczek]

Despite lodash being on the external list, certain approaches to importing from lodash increase plugin bundle size more than others.

Perhaps we can integrate some eslint-plugin-lodash rules to enforce better tree-shaking in plugins?

• https://www.npmjs.com/package/eslint-plugin-lodash
• https://github.com/idok/eslint-plugin-lodash

Or...

• https://www.npmjs.com/package/eslint-plugin-tree-shaking
• https://github.com/lukastaegert/eslint-plugin-tree-shaking

[jackw]

Unless I'm missing something here, I don't think we want to do this as importing from lodash via subpaths (import something from 'lodash/something') will cause duplicate copies of lodash to be bundled with plugins where as right now if plugins stick to import something from 'lodash' they will not be bundled at all and use the shared copy from Grafana core.