It seems the library name has changed from node-google-translate-free to node-google-translate-skidz on npm. But this github project is still called -free. And packages with both names exist on npm, -free being the outdated one.

This might confuse users. It also creates problem for contributers, when you clone this repo from github it clones as -free and npm link links it with that name which the project using it isn't able to find.

Please unpublish the -free package from npm (you might need to email them to remove it entirely or have it redirected) and rename this github repo to -skidz (github handles redirects automatically I think)

Hello,

Thank you for this package. It is very useful.

Now, i have the same app running in two different machines.
One is returning "Couldn't retrieve a valid JSON response. Perhaps the API has changed, please let us know." and the other is returning the translation just fine.

Do you have any idea of what might be happening?

Please add promise support.

(Great lib btw!)

Did i need to specify charset?
How to?

Hi!
Thank you for this module. It was working great, but now it seems that Google closed that 'hole'...
However, I think it should be possible to adapt to the change.

Trying to get a japanese text from Google Translate.

I get this.

�����ɂ���'

Seems like a problem with charcode.

Couldn't retrieve a valid JSON response. Perhaps the API has changed, please let us know.

What's the problem with my application?

I'm trying to execute this code:

translate({
 q: 'text to translate',
 source: 'en',
 target: 'es'
}, function(result) {
  console.log(result);
}); 

And... output it's "texto" when should be "texto para traducir".

Google Translate API it's a paid service, I think Google is fucking this.

I'm letting you know ;)
Gracias.

I accidentally got banned by google server, what I have to do now?

In some cases I find this quite restrictive in terms of returning the translated text. Like for single words google actually returns a lot of terms (dict.terms) which are omitted, understandably, from the simple translated text result.

It would be better to get back the original API results, maybe as a second argument to the callback. Thoughts?

Is there away to download the language you want for translation so that you can have an offline support ?

Hi. Thanks for the useful library!
It would be nice to have TypeScript definitions for the library (either included in the package directly or separate in a @types/node-google-translate-skidz package) 🚀

https://www.npmjs.com/package/node-google-translate-skidz?activeTab=dependencies