I've setup eslint with google style and found the following code being flagged with `new-cap`:

```js
import {Deserialize} from 'cerialize';

//...

const someVar = Deserialize(someJson, someType);

```

[![enter image description here](https://i.stack.imgur.com/XQGHI.png)](https://i.stack.imgur.com/XQGHI.png)

Well the notion makes sense, eslint wants it to be camelCased. But that's 3rd party code and I don't really have a good fix against it.

1. I don't want to disable new-cap rule globally because I'm willing to enforce that rule in my code.
2. I don't want to `// eslint-disable-next-line` every call on that function, because it feels pretty dumb.
3. Nor to alias every import for the same reason: `import {Deserialize as deserializeFunc} from 'cerialize';`

The fundamental question is, why is the rule checked against the caller? My code doesn't seem to be blamed, it's a callee from another library who's not following that naming rule. Of course it's not even their responsibility because the author of that library might be using other coding style.

Is eslint designed to force me to ban libraries that doesn't have the same style? Or is there any fix or [options](https://eslint.org/docs/rules/new-cap) that I'm missing?