g-plane on browser-test-update
Chore: simplify Node.js modules… (compare)
eslint-plugin-optional-chaining
to the plugin section of your config? or did eslint just infer that it should be there when you installed the babel plugin? (i don't use babel so just feeling around in the dark here to try to understand why it's looking for the plugin)
keyword-spacing
but for line breaks instead of spaces?
cannot find module
errors. we've got a shared eslint config (https://github.com/stellar/product-conventions/blob/master/packages/eslint-config/package.json) but unless i install those deps manually in the project that's using that config, eslint complains it can't find it
it's not a monorepo or anything, i've just got
module.exports = {
extends: ["@stellar/eslint-config"],
rules: {
"import/no-unresolved": 0,
},
};
in .eslintrc.js
locally. gatsby site
node_modules
might vary (I’m not sure how it decides).