@nzakas This isn't necessarily specific to this rule, but should we allow users to specify their target context:

`$ eslint -t node my-node-file.js`

If so, maybe we could modify the config JSON a bit such that based on the target context only the applicable rules are loaded:

```js
{
    rules: {
        shared: {
            // Rules that apply to all contexts.
        },

        node: {
            // Rules for the NodeJS context only.
        },

        browser: {
            // Rules for the browser context only.
        }
    }
}
```

Could be nice to be able to auto-load default node-only rules, however it does add some complexity that might not be desired. Thoughts?