Gathering detailed insights and metrics for @maxim_mazurok/gapi.client.memcache-v1beta2
Gathering detailed insights and metrics for @maxim_mazurok/gapi.client.memcache-v1beta2
Gathering detailed insights and metrics for @maxim_mazurok/gapi.client.memcache-v1beta2
Gathering detailed insights and metrics for @maxim_mazurok/gapi.client.memcache-v1beta2
npm install @maxim_mazurok/gapi.client.memcache-v1beta2
Module System
Unable to determine the module system for this package.
Min. Node Version
Typescript Support
Node Version
NPM Version
49 Stars
2,372 Commits
10 Forks
4 Watching
18 Branches
7 Contributors
Updated on 24 Nov 2024
TypeScript (99.21%)
JavaScript (0.54%)
Shell (0.26%)
Cumulative downloads
Total Downloads
Last day
2.1%
147
Compared to previous day
Last week
13.8%
1,055
Compared to previous week
Last month
-7.7%
4,253
Compared to previous month
Last year
573.6%
59,028
Compared to previous year
2
Generate TypeScript type definitions for all Google APIs, using Google API discovery service.
Meant to be used with Google APIs JavaScript Browser Client, aka gapi
.
Not to be mistaken with NodeJS Server Client which is already in TS; details
resource
and second-argument approaches; details"repeated": true
; detailsUse the supported Node version via Node Version Manager:
1nvm install
Install dependencies:
1npm install
Generate type definitions for:
all discovered Google APIs:
1npm start
Some APIs are disabled or not fully developed yet, so some expected errors might be output.
one service by name:
1npm start "--" --service sheets
where sheets
is the name of the Google Sheets service.
one service by URL:
1npm start "--" --url "https://sheets.googleapis.com/$discovery/rest?version=v4"
Note that we have to use $
- full-width dollar sign instead of the regular $
, it will be replaced by the script, this is to avoid complications with escaping of $discovery
.
1npm run compile
1node dist/cli.js --out ./types
Tests are run automatically in practice via GitHub Actions continuous integration.
Here's how to sync (add new and remove obsolete) Google APIs to/from @types/gapi.client.* namespace in DefinitelyTyped:
~
npm run apis-sync-helper
will update allowed list in DT-tools (only adds new packages and removes ones that are no longer in DT)npm run start-dt
will update DTIdeally, this should be automated in #401
The generated type definitions are linted via dtslint
, mimicking
DefinitelyTyped's process.
A single project can be linted via:
1npm run dtslint types/<project-directory>
All projects can be linted in parallel via:
1GAPI_MAX_PARALLEL=3 npm run lint
Unit tests for this generator project are written with Vitest. They can be run via:
1npm run test
This project leverages Google's TypeScript Style (gts) to standardize formatting.
To invoke the automatic code fixer, run:
1npm run fix
Do not publish types to DT directly
We've switched to publishing "real" types to npm as @maxim_mazurok/gapi.client.*
and then referencing them in @types/gapi.client.*
so that we can release updates automatically and quickly, without using too many human resources of DT.
See Syncing gapi client namespace in DT with available APIs section for instructions.
Every hour, type definitions are generated, linted, tested, and published to NPM.
First approach (Resource):
1gapi.client.sheets.spreadsheets.batchUpdate({ 2 spreadsheetId: 'someId', 3 resource: { 4 // Request Body goes here, as part of `request` 5 }, 6});
second approach (Body):
1gapi.client.sheets.spreadsheets.batchUpdate( 2 { 3 spreadsheetId: 'someId', 4 }, 5 { 6 // Request Body goes here, as a second argument 7 } 8);
Both approaches are valid (tested for Google Sheets API), but the first one seems to be the default for JS Client Library.
More info here: google/google-api-javascript-client#432 (comment),
and here: declanvong@bec4f89
#r35992626
NOTE: Some APIs have methods that accept resource
parameter that is not the request body. In that case, we only generate the second approach (details)
This fork keeps interfaces even if they are empty to make typings more accurate.
More info here: Maxim-Mazurok/google-api-typings-generator#4
This fork understands "repeated": true
More info here: Maxim-Mazurok/google-api-typings-generator#1
and here: declanvong@bec4f89
#r35992626
There are two ways to use Google APIs: on the client-side (in the browser) and on the server-side.
The client-side library, called gapi
is kinda closed-source.
We can see compiled (unreadable minified) JS code of the client-side library.
When you use any Google JS API, you use gapi
. It loads library definitions from Google API Discovery Service
and generates all API calls on the fly.
So, there's no TS version of gapi
because it's closed-source
and other client libraries do not exist, because they are being generated on the fly by gapi
.
If you want to use TypeScript with gapi
- you have to use type definitions generated by this project.
While we do generate typings for Google APIs, we can't generate gapi
typings from discovery, so we rely on
@types/gapi and you also should.
The server-side libraries are open-sourced and are available here. Since they are written in TS, you don't need any additional type definitions to use them.
The error looks like this (see #483):
$ npm install @types/gapi.client.YOUR_API@v2 --save-dev
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@types%2fgapi.client.YOUR_API - Not found
npm ERR! 404
npm ERR! 404 '@types/gapi.client.YOUR_API@v2' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
It's most likely caused by your API package not being published to NPM yet.
To fix this - open an issue and I'll update the list of supported APIs.
Later on, when #401 is closed - this process will be automated.
Also, you can use these types from the types branch
No vulnerabilities found.
Reason
26 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
SAST tool is run on all commits
Details
Reason
2 existing vulnerabilities detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More