Benjamin E. Coe
Benjamin E. Coe
@CoolDCB I would expect your initialization logic to look more like this: ```js const {google} = require('googleapis'); const compute = google.compute('v1'); async function main () { const auth = new...
> I created [a repo](https://github.com/KiritaniAyaka/istanbul-coverage-report) for repro this. My lib is using vitest (vitest depends istanbul indirectly) so I created 2 branches for repro of istanbul and vitest. In your...
@vamcc this library should be supporting `NO_PROXY`, could you provide a minimal example that is failing for you?
> I think adding a tiny chart to help digesting the spec would be helpful. @damianopetrungaro I agree, at work I try to distill conventional commits down to fundamentals when...
Just a quick drive by comment, I like @javier-godoy's approach of creating a stricter specification on top of conventional commits. This was my original intention regarding the relationship between the...
The challenge with aliasing the foundational types (`fix` and `feat`), is that there's a significant ecosystem of tooling that exists already for conventional commits. Perhaps we could instead provide more...
@rommguy are you able to import the APIs that you're using individually, as @yjwong suggests. I believe this is partially a documentation problem, as we should be documenting this as...
@rommguy I believe you can use an API directly like this: ```js import {iam_v1 as v1} from "googleapis/build/src/apis/iam/v1"; const client = new v1.Iam({}); ``` Let me know if this works...
@sgb-io @rommguy we have now also started publishing individual modules for any libraries in googleapis that don't have an alternative client: * https://www.npmjs.com/package/@googleapis/sheets * https://www.npmjs.com/package/@googleapis/iam Give these a shot, rather...
>But even if we manage to find it on https://github.com/googleapis/google-cloud-node/blob/main/packages/google-cloud-compute/CHANGELOG.md it contains just one line: "new generated version of compute API (https://github.com/googleapis/google-cloud-node/issues/537)" and that's all! Not very comprehensive isn't it?...