npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@google-cloud/telcoautomation

v0.5.1

Published

Telco Automation API client for Node.js

Readme

Telco Automation 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

npm version

Telco Automation 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

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the Telco Automation API API.
  4. Set up authentication so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/telcoautomation

Samples

Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

| Sample | Source Code | | --------------------------- | --------------------------------- | | cloud | source code | | apply deployment | source code | | apply hydrated deployment | source code | | approve blueprint | source code | | compute deployment status | source code | | create blueprint | source code | | create deployment | source code | | create edge slm | source code | | create orchestration cluster | source code | | delete blueprint | source code | | delete edge slm | source code | | delete orchestration cluster | source code | | discard blueprint changes | source code | | discard deployment changes | source code | | get blueprint | source code | | get deployment | source code | | get edge slm | source code | | get hydrated deployment | source code | | get orchestration cluster | source code | | get public blueprint | source code | | list blueprint revisions | source code | | list blueprints | source code | | list deployment revisions | source code | | list deployments | source code | | list edge slms | source code | | list hydrated deployments | source code | | list orchestration clusters | source code | | list public blueprints | source code | | propose blueprint | source code | | reject blueprint | source code | | remove deployment | source code | | rollback deployment | source code | | search blueprint revisions | source code | | search deployment revisions | source code | | update blueprint | source code | | update deployment | source code | | update hydrated deployment | source code | | cloud | source code | | apply deployment | source code | | apply hydrated deployment | source code | | approve blueprint | source code | | compute deployment status | source code | | create blueprint | source code | | create deployment | source code | | create edge slm | source code | | create orchestration cluster | source code | | delete blueprint | source code | | delete edge slm | source code | | delete orchestration cluster | source code | | discard blueprint changes | source code | | discard deployment changes | source code | | get blueprint | source code | | get deployment | source code | | get edge slm | source code | | get hydrated deployment | source code | | get orchestration cluster | source code | | get public blueprint | source code | | list blueprint revisions | source code | | list blueprints | source code | | list deployment revisions | source code | | list deployments | source code | | list edge slms | source code | | list hydrated deployments | source code | | list orchestration clusters | source code | | list public blueprints | source code | | propose blueprint | source code | | reject blueprint | source code | | remove deployment | source code | | rollback deployment | source code | | search blueprint revisions | source code | | search deployment revisions | source code | | update blueprint | source code | | update deployment | source code | | update hydrated deployment | 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/telcoautomation@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