Giter Club home page Giter Club logo

google-translate-api's Introduction

google-translate-api-x

Actions Status NPM version

A free and unlimited API for Google Translate 💵 🚫 written with compatibility in mind, made to be crossplatform.

Features

  • Up-to-Date with all new Google Translate supported languages!
  • Auto language detection
  • Spelling correction
  • Language correction
  • Fast and reliable – it uses the same servers that translate.google.com uses
  • Wide compatibility through supporting Fetch and custom request functions
  • Batch many translations into one request with arrays or objects!
  • Supports the single and batch translate endpoints
  • Has both a translate method, and a Translator class which preserves options
  • Text-to-Speech from the Google Translate API using the speak method

Why this fork?

This fork of vitalets/google-translate-api contains several improvements with the primary change being it is written to support both the batch and single Google Translate endpoints, as well as any input request function. Additionally, there is optional language checking, and a list of supported languages that can best used. Many similar packages of the same endpoints either only use the single translate endpoint, which is quickly rate limited, or the batch translate endpoint which is sometimes innaccurate.

Install

npm install google-translate-api-x

Usage

From automatic language detection to English:

const translate = require('google-translate-api-x');
// Or of course
import translate from 'google-translate-api-x';
// Or deconstruct all the exposed variables as
import { translate, Translator, speak, singleTranslate, batchTranslate, languages, isSupported, getCode } from 'google-translate-api-x';
// or again
const { translate, Translator, speak, singleTranslate, batchTranslate, languages, isSupported, getCode } = require('google-translate-api-x');

const res = await translate('Ik spreek Engels', {to: 'en'});

console.log(res.text); //=> I speak English
console.log(res.from.language.iso);  //=> nl

If server returns Response code 403 (Forbidden) try set option client=gtx:

const res = await translate('Ik spreek Engels', { to: 'en', client: 'gtx' }).then(res => { ... });

Please note that maximum text length for translation call is 5000 characters. In case of longer text you should split it on chunks, see #20.

Autocorrect

From English to Dutch with a typo (autoCorrect):

const res = await translate('I spea Dutch!', { from: 'en', to: 'nl', autoCorrect: true });

console.log(res.from.text.didYouMean); // => false
console.log(res.from.text.autoCorrected); // => true
console.log(res.from.text.value); // => 'I [speak] Dutch!'

console.log(res.text); // => 'Ik spreek Nederlands!'

These reported values are often inaccurate and cannot be relied upon

Text-to-Speech (TTS)

A TTS request is made just like a translate request but using the speak method. The language spoken is the to language in options(or query params). The response is just a Base64 MP3 as a string.

import { speak } from 'google-translate-api-x';
import { writeFileSync } from 'fs';

const res = await speak('gata', {to: 'es'}); // => Base64 encoded mp3
writeFileSync('cat.mp3', res, {encoding:'base64'}); // Saves the mp3 to file

Single and Batch Endpoints

Single translate

The single translate endpoint is generally more accurate- and I suspect is a more advanced translation engine. Noticably it is more accurate(but still not completely accurate) when it comes to gendered words. Using the more accurate single translate endpoint requires setting forceBatch to false:

const res = await translate('cat', {to: 'es', forceBatch: false});

console.log(res.test); // => 'gato' instead of 'gata' which batch would return

And to guarantee it is used you can also pass fallbackBatch: false.

⚠️However, the single translate endpoint is much more likely to be ratelimited and have your request rejected than the batch translate endpoint!

Batch translate

Because of the risk of being ratelimited- the default endpoint and fallback endpoint for this package is the batch translate endpoint. It notably supports multiple queries in one request- so batch requests always go through the batch endpoint.

Persistent Options with Translator class

import { Translator } from 'google-translate-api-x';
const translator = new Translator({from: 'en', to: 'es', forceBatch: false, tld: 'es'});
const cat = await translator.translate('cat');
const dog = await translator.translate('dog');
const birds = await translator.translate(['owl', 'hawk']);

console.log(cat.text); // => 'gato'
console.log(dog.text); // => 'perro'
console.log([birds[0].text, birds[1].text]); // => '[ 'búho', 'halcón' ]'

Did you mean

Even with autocorrect disabled Google Translate will still attempt to correct errors, but will not use the correction for translation. However, it will update res.from.text.value with the corrected text:

const res = await translate('I spea Dutch!', { from: 'en', to: 'nl', autoCorrect: false });

console.log(res.from.text.didYouMean); // => true
console.log(res.from.text.autoCorrected); // => false
console.log(res.from.text.value); // => 'I [speak] Dutch!'

console.log(res.text); // => 'Ik speed Nederlands!'

Array and Object inputs (Batch Requests)

An array or object of inputs can be used to slightly lower the number of individual API calls:

const inputArray = [
  'I speak Dutch!',
  'Dutch is fun!',
  'And so is translating!'
];

const res = await translate(inputArray, { from: 'en', to: 'nl' });

console.log(res[0].text); // => 'Ik spreek Nederlands!'
console.log(res[1].text); // => 'Nederlands is leuk!'
console.log(res[2].text); // => 'En zo ook vertalen!'

and similarly with an object:

const inputObject = {
  name: 'Aidan Welch',
  fact: 'I\'m maintaining this project',
  birthMonth: 'February'
};

const res = await translate(inputObject, { from: 'en', to: 'ja' });

console.log(res.name.text); // => 'エイダンウェルチ'
console.log(res.fact.text); // => '私はこのプロジェクトを維持しています'
console.log(res.birthMonth.text); // => '2月'

If you use auto each input can even be in a different language!

Batch Request with Different Options (Option Query)

In Array and Object requests you can specify from, to, forceFrom, forceTo, and autoCorrect for each individual string to be translated by passing an object with the options set and the string as the text property. Like so:

const inputArray = [
  'I speak Dutch!',
  {text: 'I speak Japanese!', to: 'ja'},
  {text: '¡Hablo checo!', from: 'es', to: 'cs', forceTo: true, autoCorrect: true}
];

const res = await translate(inputArray, { from: 'en', to: 'nl' });

console.log(res[0].text); // => 'Ik spreek Nederlands!'
console.log(res[1].text); // => '私は日本語を話します!'
console.log(res[2].text); // => 'Mluvím česky!'

⚠️ You cannot pass a single translation by itself as an option query, it must either be passed as a string and use the options parameter, or passed wrapped by another array or object. This the translate function cannot differentiate between a batch query object and an option query object.

Using languages not supported in languages.js yet

If you know the ISO code used by Google Translate for a language and know it is supported but this API doesn't support it yet you can force it like so:

const res = await translate('Hello!', { from: 'en', to: 'as', forceTo: true });

console.log(res.text); // => 'নমস্কাৰ!'

forceFrom can be used in the same way.

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

translate = require('google-translate-api-x');
translate.languages['sr-Latn'] = 'Serbian Latin';

translate('translator', {to: 'sr-Latn'}).then(res => ...);

Proxy

Google Translate has request limits(supposedly for batch- and definitely for single translate). If too many requests are made, you can either end up with a 429 or a 503 error. You can use proxy to bypass them, the best way is to pass a proxy agent to fetch through requestOptions:

npm install https-proxy-agent
import HttpsProxyAgent from require('https-proxy-agent');
translate('Ik spreek Engels', {to: 'en', requestOptions: {
    agent: new HttpsProxyAgent('proxy-url-here');
  }
}).then(res => {
    // do something
});

Does it work from web page context?

It can, sort of. https://translate.google.com does not provide CORS http headers allowing access from other domains. However, this fork is written using Fetch and/or Axios, allowing contexts that don't request CORS access, such as a browser extension background script or React Native.

API

translate(input, options)

input

Type: string | string[] | {[key]: string} | {text: string, ...options}[] | { [key]: {text: string, ...options} }

The text to be translated, with optionally specific options for that text

Returns an object | object[] | {[key]: object}}:

Matches the structure of the input, so returns just the individual object if just a string is input, an array if an array is input, object with the same keys if an object is input. Regardless of that, each returned value will have this schema:

  • 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 and did not autoCorrect
  • 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 ([ ]):

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

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

speak(input, options)

input

Type: string | string[] | {[key]: string} | {text: string, ...options}[] | { [key]: {text: string, ...options} }

The text to be spoken, with optionally specific options for that text.

The to field of options is used for the language spoken in

Returns a string | string[] | {[key]: string}}:

The returned string is a Base64 encoded mp3.

Translator(options)

Returns a translator:

An object with these options as the default, that you can call the translate method on.

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.cjs.

to

Type: string Default: en

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

forceFrom

Type: boolean Default: false

Forces the translate function to use the from option as the iso code, without checking the languages list.

forceTo

Type: boolean Default: false

Forces the translate function to use the to option as the iso code, without checking the languages list.

forceBatch

Type: boolean Default: true

Forces the translate function to use the batch endpoint, which is less likely to be rate limited than the single endpoint.

fallbackBatch

type: boolean Default: true

Enables falling back to the batch endpoint if the single endpoint fails.

autoCorrect

Type: boolean Default: false

Autocorrects the inputs, and uses those corrections in the translation.

rejectOnPartialFail

Type: boolean Default: true

When true rejects whenever any translation in a batch fails- otherwise will just return null instead of that translation.

raw

Type: boolean Default: false

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

requestFunction

Type: function Default: fetch

Function inputs should take (url, requestOptions) and mimick the response of the Fetch API with a res.text() and res.json() method.

client

Type: string Default: "t"

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

tld

Type: string Default: "com"

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

requestOptions

Type: object

The options used by the requestFunction. Must be in the style of fetchinit.

Related projects

License

MIT © Matheus Fernandes, forked and maintained by Aidan Welch.

google-translate-api's People

Contributors

6ebeng avatar abhinandanudupa avatar adam-clrk avatar aidanwelch avatar arthurlacoste avatar ciiiii avatar dougley avatar eyelly-wu avatar jukeboxrhino avatar matheuss avatar noname001 avatar olavoparno avatar rawr51919 avatar tgyou avatar tobiasmuehl avatar usrtax avatar vitalets avatar vkedwardli avatar xfslove avatar yuler avatar zihadmahiuddin avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar

google-translate-api's Issues

Can't run on React.js

The error:
TypeError: google_translate_api_x__WEBPACK_IMPORTED_MODULE_1__ is not a function

I've tried using this library on vanilla js and it works just fine. But when I tried it on React it keeps getting error like in the above even I use the simpliest method to use this library. Is there any settings that I have to apply first in my React project before using this library?
Sorry for my english and I'm new to React and JavaScript, so it will be so kind of you if you can give me an assistance.

Btw, thanks for providing this library

AxiosError: Request failed with status code 429

Issue 12 wasn't finished being addressed before it was closed. My app wouldn't hit the rate limit as it sends fewer than 20 requests per day.

Error code 429 is a "too many requests" error. I would assume that your API has a Google Translate API key tied to it? My immediate thought is there are too many users on this "free api" causing the interface to hit the rate limit.

Real-time translation

Can this package translate in real-time, like users don't need to press the translate button to translate, but just need to type and wait for it to auto translate?

`res.from.language.didYouMean` is always true

When I use the Google Translate website from English to Dutch, and enter the Dutch word "Kaartspel" in the English from box, it shows "Translate from: Dutch":

Screenshot 2024-06-13 at 11 18 32

See: https://translate.google.com/?sl=en&tl=nl&text=Kaartspel&op=translate

When I use this API:

const res = await translate('Kaartspel', { from: 'en', to: 'nl', autoCorrect: true, requestFunction: fetch});
console.log(res.from.language.didYouMean);
console.log(res.from.language.iso);

It prints:

true
nl

This is correct ✅

Repeat with a correct English "Card game", there is no warning in the portal:

Screenshot 2024-06-13 at 11 24 08

See: https://translate.google.com/?sl=en&tl=nl&text=Card%20game&op=translate

When I use this API:

const res = await translate('Card game', { from: 'en', to: 'nl', autoCorrect: true, requestFunction: fetch});
console.log(res.from.language.didYouMean);
console.log(res.from.language.iso);

It prints:

true
en

Although res.from.language.iso changed correctly to "en", res.from.language.didYouMean is still true.
This is incorrect ❌

fetch is not defined after deployment

@AidanWelch This package works fine when I start my server in terminal, but as soon as I deploy to Render it says ERROR ReferenceError: fetch is not defined at Object.requestFunction (/opt/render/project/src/node_modules/google-translate-api-x/lib/defaults.cjs:9:36), seems it isn't truly cross-platform or is there something I could do different to get it to work in a pure Node environment?

All the help will be appreciated and the batching feature is truly an improvement on the vitalets package. Thank you! ✨

Big translation slowed down

Hi @AidanWelch, thanks for an amazing package!
One thing I noticed in the past day or two is that a big translation (like full song lyrics) considerably slowed down. It used to be almost instant, but now it's taking up to 15 seconds.
When I try vitalets package, it is still almost instant. Do you know of any reason this might be happening?

I'm using a Next.js project, still on Next 12 using an API route (server side). Is there any way to test the speed of the actual package? Thanks!

Caught an error from batch translate

Hi @AidanWelch

I caught a new error from the below codes.

trInput is an array for batch translation.

It doesn't happen all the time, maybe 1 out of 4 or 5 times. Even when all the variable values are exactly the same for all the 4 or 5 times.

    const translation = await translate(trInput, {from: userLanguage, to: addHelperLanguage && helperLanguage, autoCorrect: true})
                                .catch((error) => {
                                    console.error('translate| translate-google-api-x error: ', error.message)
                                    throw error
                                });

Error caught in below

translate| translate-google-api-x error:  Cannot read properties of null (reading '1')
Url: https://translate.google.com/_/TranslateWebserverUi/data/batchexecute?rpcids=MkEWBc&source-path=%2F&f.sid=3998618730767360818&bl=boq_translate-webserver_20230409.08_p0&hl=en-US&soc-app=1&soc-platform=1&soc-device=1&_reqid=7749&rt=c

The value returned from the Url in the error in below

)]}'

103
[["er",null,null,null,null,405,null,null,null,9],["di",17],["af.httprm",17,"-2930294764364961249",6]]
25
[["e",4,null,null,139]]

CORS policy

I'm using ReactJs.
When I use the request example. I'm getting CORS error.

import translate from 'google-translate-api-x';

const res = await translate('Ik spreek Engels', { to: 'en' });

console.log(res.text); //=> I speak English
console.log(res.from.language.iso);  //=> nl

That code return

Access to fetch at 'https://translate.google.com/' from origin 'http://localhost:5173' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Is that an API error or I need to use some param on the request translate()?

  • with node that error doesn't occur.

CORS policy error

i installed your package and tried the description but unfortunately i get errors about CORS error, and i don't know how to solve it

Discrepancy with Google Translation

Hi Aidan,

Loving the API so far!

I did have one issue, when I'm translating something from Hebrew to English, I'm getting a different translation from Google Translate. The one the API is giving me is incorrect, and the one Google Translate gives me is much better. Do you think I'm using it wrong, or have you seen inconsistencies with Google Translate's website?

This is my prompt from the translate call, which returns this result: "Aryan main, I would like to the mountains at the distance"
image
However, this is what Google translate returns: "I lift my head, I will lift my eyes to the mountains in the distance"

Any ideas about this? I've also been having this issue with some other languages, but this is one that I found right now. Thanks so much!

Batch translation error

Error Info

Partial Translation Request Fail: at least one translation failed, it was either invalid or more likely- rejected by the server. You can try the request again and if it persists try a proxy, spacing out requests, and/or using a different tld. If you would like to translate other requests in a batch translation even if one fails(the failed translation will be set to null) pass the option rejectOnPartialFail: false. You can also try using the singleTranslate endpoint with: forceBatch: false

A reproducible example
https://runkit.com/eyelly/64787340c932b600084ae8ee

Thanks to the author for providing this tool library, hope this problem can be fixed

Autocorrect example provides different output

The documentation example from https://github.com/AidanWelch/google-translate-api?tab=readme-ov-file#autocorrect shows different output than the API.

Documentation

const res = await translate('I spea Dutch!', { from: 'en', to: 'nl', autoCorrect: true });

console.log(res.from.text.didYouMean); // => false
console.log(res.from.text.autoCorrected); // => true
console.log(res.from.text.value); // => 'I [speak] Dutch!'

console.log(res.text); // => 'Ik spreek Nederlands!'

Output of version 10.6.8

const res = await translate('I spea Dutch!', { from: 'en', to: 'nl', autoCorrect: true });

console.log(res.from.text.didYouMean); // => true
console.log(res.from.text.autoCorrected); // => false
console.log(res.from.text.value); // => 'I [speak] Dutch!'

console.log(res.text); // => 'Ik speed Nederlands!'

So the flags didYouMean and autoCorrected are exactly opposite, and the res.text is not corrected, despite autoCorrect: true.

UPDATE

It did autocorrect while using "Card gaame" as English source text with a typo:

const res = await translate('Card gaame', { from: 'en', to: 'nl', autoCorrect: true });

console.log(res.from.text.didYouMean); // => false
console.log(res.from.text.autoCorrected); // => true
console.log(res.from.text.value); // => 'Card [game]'

console.log(res.text); // => 'Kaartspel'

After reading the description of the returned parameters more thoroughly, it's important to realise that although autoCorrect: true is requested, Google might not be able to correct it.
In that case it will return res.from.text.autoCorrected = false and a possibly incorrect translation in res.text.

Maybe it's an idea to update the example in the docu, since it does not reflect the API output.

It throws error "fetch is not defined"

My demo is simple , just like this.

(async() => {
    const translate = require('google-translate-api-x');
    const res = await translate('Ik spreek Engels', {to: 'zh'});
    console.log(res.text);
})()

When run the code, it throws the error

image

ERROR [TypeError: Cannot convert null value to object]

Hello, I am getting the error in the title while translating text. I suspected it because I was using texts dynamically. Then I tried to translate the texts statically but this error returns 1 time out of 5 translations (same text).

Autocorrect not properly applied to translations from certain networks

Certain networks require the X-Goog-BatchExecute-Bgr header to be sent on requests, or the autocorrect will not be applied to some translations(seemingly typos where a letter is dropped, such as "I spea Dutch!" instead of "I speak Dutch!").

The code for generating this header I believe is found in this static script.

I believe in xH.prototype.s()

This would likely take a while to fix.

Getting Weird Translation

Hi im not getting the same result when i translate in google translate and using google-translate-api.
What might be the issue?

TypeScript Error

TS2339: Property 'text' does not exist on type 'ITranslateResponse | ITranslateResponse[] | { [x: string]: ITranslateResponse; }'.   Property 'text' does not exist on type 'ITranslateResponse[]'.

I use React and TypeScript.

const translator = new Translator({from: 'en', to: 'es', forceBatch: false, tld: 'es'}); const res = await translator.translate('Ik spreek Engels', {to: user_data!.lang}); console.log(res.text)

Issue with the speak functionality

New to development,
I am getting this error
/node_modules/google-translate-api-x/lib/speak.cjs:66 const result = JSON.parse(translation[2])[0]; ^ TypeError: Cannot read properties of null (reading '0')

I figured it out , the issue appears when the text under single translate using "speak" function exceeds 195 characters.
I need help how to convert long texts to mp3.

There are other packages that are able to convert it, but I really wanted to make this package more efficient by adding inputs.

Thanks

change speak speed

is there any way to change the speak (tts) speed? its talking a bit slow

ReferenceError: fetch is not defined

/root/***/node_modules/google-translate-api-x/lib/defaults.cjs:9
        requestFunction: fetch,
                         ^

ReferenceError: fetch is not defined
    at Object.<anonymous> (/root/***/node_modules/google-translate-api-x/lib/defaults.cjs:9:19)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/root/***/node_modules/google-translate-api-x/lib/translate.cjs:2:29)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)

Obtain translation synonyms

Is there to obtain the synonyms of a word translation. For example, let's say the preposition mit in German, which can be in multiple ways in English. Is there to obtain all of those possible translations?
Thanks!

requestOptions documentation outdated

google-translate-api#proxy

code:

const tunnel = require('tunnel');
const translate = require('google-translate-api-x');

translate('Ik spreek Engels', { to: 'en', tld: 'jp' }, {
    agent: tunnel.httpsOverHttp({
        proxy: {
            host: '127.0.0.1', // ip
            port: '7890', // port
        }
    }
    )
}).then(res => {
    console.log(res)
    // do something
});

console:

PS C:\Users\Administrator\Desktop\NodejsProjects> node .
node:internal/deps/undici/undici:14062
    Error.captureStackTrace(err, this);
          ^

TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:14062:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async runBatch (C:\Users\Administrator\Desktop\NodejsProjects\node_modules\google-translate-api-x\lib\translate.cjs:7:19) {
  cause: ConnectTimeoutError: Connect Timeout Error
      at onConnectTimeout (node:internal/deps/undici/undici:7897:28)
      at node:internal/deps/undici/undici:7855:50
      at Immediate._onImmediate (node:internal/deps/undici/undici:7884:37)
      at process.processImmediate (node:internal/timers:471:21) {
    code: 'UND_ERR_CONNECT_TIMEOUT'
  }
}

Node.js v18.13.0

google-translate-api-x gives below error

error: node_modules/google-translate-api-x/lib/Translator.cjs: /home/nirali/Desktop/farmerAssistantApp/node_modules/google-translate-api-x/lib/Translator.cjs: Class private methods are not enabled. Please add @babel/plugin-proposal-private-methods to your configuration.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.