Package Exports
- @google-cloud/automl
- @google-cloud/automl/build/src/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@google-cloud/automl) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Cloud AutoML API: Nodejs Client
This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority
Cloud AutoML API client for Node.js
🔔 AutoML API NodeJS Client is now available in Vertex AI. Please visit node-js-aiplatform for the new NodeJS Vertex AI client. Vertex AI is our next generation AI Platform, with many new features that are unavailable in the current platform. Migrate your resources to Vertex AI to get the latest machine learning features, simplify end-to-end journeys, and productionize models with MLOps.
Cloud AutoML API client for Node.js
A comprehensive list of changes in each version may be found in the CHANGELOG.
Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.
Table of contents:
Quickstart
Before you begin
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the Cloud AutoML API API.
- Set up authentication so you can access the API from your local workstation.
Installing the client library
npm install @google-cloud/automlSamples
Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.
| Sample | Source Code |
|---|---|
| create dataset | source code |
| create model | source code |
| delete dataset | source code |
| delete model | source code |
| deploy model | source code |
| export data | source code |
| export model | source code |
| get annotation spec | source code |
| get dataset | source code |
| get model | source code |
| get model evaluation | source code |
| import data | source code |
| list datasets | source code |
| list model evaluations | source code |
| list models | source code |
| undeploy model | source code |
| update dataset | source code |
| update model | source code |
| batch predict | source code |
| predict | source code |
| cloud | source code |
| create dataset | source code |
| create model | source code |
| delete dataset | source code |
| delete model | source code |
| deploy model | source code |
| export data | source code |
| export evaluated examples | source code |
| export model | source code |
| get annotation spec | source code |
| get column spec | source code |
| get dataset | source code |
| get model | source code |
| get model evaluation | source code |
| get table spec | source code |
| import data | source code |
| list column specs | source code |
| list datasets | source code |
| list model evaluations | source code |
| list models | source code |
| list table specs | source code |
| undeploy model | source code |
| update column spec | source code |
| update dataset | source code |
| update table spec | source code |
| batch predict | source code |
| predict | source code |
| cloud | source code |
Supported Node.js Versions
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.
Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:
- Legacy versions are not tested in continuous integration.
- Some security patches and features cannot be backported.
- Dependencies cannot be kept up-to-date.
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed through npm dist-tags.
The dist-tags follow the naming convention legacy-(version).
For example, npm install @google-cloud/automl@legacy-8 installs client libraries
for versions compatible with Node.js 8.
Versioning
This library follows Semantic Versioning.
More Information: Google Cloud Platform Launch Stages
Contributing
Contributions welcome! See the Contributing Guide.
Please note that this README.md
and a variety of configuration files in this repository (including .nycrc and tsconfig.json)
are generated from a central template.
License
Apache Version 2.0
See LICENSE