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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@danke77/google-translate-api

v1.0.0

Published

A free and unlimited API for Google Translate

Downloads

4

Readme

google-translate-api

NPM version

A free and unlimited API for Google Translate :dollar::no_entry_sign: for Node.js.

Features

  • Auto language detection
  • Spelling correction
  • Language correction
  • Fast and reliable – it uses the same servers that translate.google.com uses

Why this fork?

This fork of original matheuss/google-translate-api contains several improvements:

  • New option client="t|gtx". Setting client="gtx" seems to work even with outdated token, see this discussion for details
  • Fixed extraction of TKK ceed from current https://translate.google.com sources (via @vitalets/google-translate-token)
  • Removed unsecure unsafe-eval dependency (See #2)
  • Added support for custom tld (especially to support translate.google.cn, see #7)
  • Added support for outputting pronunciation (see #17)
  • Added support for language extensions from outside of the API (See #18)

Install

npm install @danke77/google-translate-api

Usage

From automatic language detection to English:

const Translator = require('@danke77/google-translate-api');

const translator = new Translator({
    from: 'auto',
    to: 'en',
    raw: false,
    client: 'gtx', // t
    tld: 'cn',
});

const res = await translator.translate('Ik spreek Engels')
    .catch(err => {
        console.error(err);
    });
console.log(res.text); // I speak English
console.log(res.from.language.iso); // nl

From English to Dutch with a typo:

const Translator = require('@danke77/google-translate-api');

const translator = new Translator({
    from: 'en',
    to: 'nl',
    raw: false,
    client: 'gtx', // t
    tld: 'cn',
});

const res = await translator.translate('I spea Dutch!')
    .catch(err => {
        console.error(err);
    });
console.log(res.text); // Ik spreek Nederlands!
console.log(res.from.text.autoCorrected); // true
console.log(res.from.text.value); // I [speak] Dutch!
console.log(res.from.text.didYouMean); // false

You can also add languages in the code and use them in the translation:

const Translator = require('@danke77/google-translate-api');

Translator.languages['sr-Latn'] = 'Serbian Latin';
const translator = new Translator({
    from: 'en',
    to: 'sr-Latn',
    raw: false,
    client: 'gtx', // t
    tld: 'cn',
});

Does it work from web page context?

No. https://translate.google.com does not provide CORS http headers allowing access from other domains.

API

new Translator([options])

options

Type: object

from

Type: string Default: auto

The text language. Must be auto or one of the codes/names (not case sensitive) contained in languages.js

to

Type: string Default: zh-CN

The language in which the text should be translated. Must be one of the codes/names (case sensitive!) contained in languages.js.

raw

Type: boolean Default: false

If true, the returned object will have a raw property with the raw response (string) from Google Translate.

client

Type: string Default: "gtx"

Query parameter client used in API calls. Can be t|gtx.

tld

Type: string Default: "cn"

TLD for Google translate host to be used in API calls: https://translate.google.{tld}.

translate(text)

text

Type: string

The text to be translated

Returns an object:

  • text (string) – The translated text.
  • from (object)
    • language (object)
      • didYouMean (boolean) - true if the API suggest a correction in the source language
      • iso (string) - The code of the language that the API has recognized in the text
    • text (object)
      • autoCorrected (boolean)true if the API has auto corrected the text
      • value (string) – The auto corrected text or the text with suggested corrections
      • didYouMean (boolean)true if the API has suggested corrections to the text
  • raw (string) - If options.raw is true, the raw response from Google Translate servers. Otherwise, ''.

Note that res.from.text will only be returned if from.text.autoCorrected or from.text.didYouMean equals to true. In this case, it will have the corrections delimited with brackets ([ ]):

const res = await translator.translate('I spea Dutch!')
    .catch(err => {
        console.error(err);
    });
console.log(res.from.text.value); // I [speak] Dutch!

Otherwise, it will be an empty string ('').

License

MIT