Product
Introducing Java Support in Socket
We're excited to announce that Socket now supports the Java programming language.
Convert text to different languages on Node.js and the browser. Flexible package that allows you to use Google (default), Yandex, Libre or DeepL:
import translate from "translate";
translate.engine = "deepl";
translate.key = process.env.DEEPL_KEY;
const text = await translate("Hello world", "es");
console.log(text);
// "Hola mundo"
This package can be used in Node.js and on the browser. First thing install the library:
npm install translate
Then import it to use it:
import translate from "translate";
Alternatively for the browser you can use Jsdelivr CDN with the UMD export:
<script
type="module"
src="https://cdn.jsdelivr.net/npm/translate/index.min.js"
></script>
After including translate the usage is similar for both Node.js and the browser. Now you have to set which engine you want to use (default is 'google'), and the key for it if needed:
translate.engine = "deepl"; // "google", "yandex", "libre", "deepl"
translate.key = process.env.DEEPL_KEY;
Then you can use it. Putting it all together:
// Omit this line if loading from a CDN
import translate from "translate";
translate.engine = "deepl"; // "google", "yandex", "libre", "deepl"
translate.key = process.env.DEEPL_KEY;
const text = await translate("Hello world", "es");
console.log(text);
// "Hola mundo"
Here is a list of all the options. They all can be set on the root instance like translate[key] = value
and when creating a new instance const t = Translate({ ... })
. The function has this signature:
translate(text: string, to: string): Promise<string>
translate(text: string, { to: string, from: string }): Promise<string>
These are all of the options:
to
: the string of the language to translate to. It can be in any of the two ISO 639 (1 or 2) or the full name in English like Spanish
. Defaults to en.from
: the string of the language to translate to. It can be in any of the two ISO 639 (1 or 2) or the full name in English like Spanish
. Also defaults to en.cache
*: a Number
with the milliseconds that each translation should be cached. Leave it undefined to cache it indefinitely (until a server/browser restart).engine
* (& engines
): a String
containing the name of the engine to use for translation. Right now it defaults to google
. Read more in the engine section.key
* (& keys
): the API Key for the engine of your choice. Read more in the engine section.url
*: only available for those engines that you can install on your own server (like Libretranslate), allows you to specify a custom endpoint for the translations. See this issue for more info.* The options marked as can only be set to the root
translate.cache = 1000
or when creating a new instanceconst myDeepL = translate.Translate()
, but not as the second parameter.
Examples:
// Translate from English (default) to Spanish (specified)
const foo = await translate("Hello world", "es");
// Same as this:
const bar = await translate("Hello world", { to: "es" });
You can change the options in 3 ways. First, for the simple from
and to
options, set them as the second argument:
import translate from "translate";
translate("Hello world", "es");
translate("Hola mundo", { from: "en", to: "es" });
You can also change the default options straight on the base instance, which should be common for the shared options such as the API key, engine, etc:
import translate from "translate";
// Configure it, setting the "from" to "Spanish" as default!
translate.from = "es";
translate.engine = "deepl";
translate.key = process.env.DEEPL_KEY;
// Use it
await translate("Hola mundo", "ja");
Finally, you can combine multiple instances of Translate, which is useful to have different caches, or use different engines at the same time:
// Import the constructor
import { Translate } from 'translate';
// Create an instance
const myLib = Translate({ engine: 'deepl', from: 'es', ... });
// Use it
await myLib("Hola mundo", "ja" );
Several translating engines are available to translate your text:
google
: (demo | docs): Google Translate.yandex
: (demo | docs | API Key): Yandex Translatelibre
: (demo): An independent translation engine. You can use the official website or install it on your own server.deepl
: (demo): A rapidly growing popular translation engine built with Machine Learning.To get the API Key you will be signing some contract with these services; it's your responsibility to follow these and we are not liable if you don't as explained in our MIT License.
Once you get the API key and if you are only going to be using one engine (very likely), we recommend setting this globally for your whole project:
import translate from "translate";
translate.engine = "deepl";
translate.key = "YOUR-KEY-HERE";
// ... use translate()
If you are in Node.js, this likely comes from an environment variable:
import translate from "translate";
translate.engine = "deepl";
translate.key = process.env.TRANSLATE_KEY;
// ... use translate()
You can create different instances if you want to combine different engines:
import { Translate } from "translate";
const gTranslate = Translate({ engine: "google", key: "..." });
const dTranslate = Translate({ engine: "deepl", key: "..." });
const lTranslate = Translate({ engine: "libre", key: "..." });
Specifically in Libretranslate, you can also add a url
parameter if you install it on your own server:
translate.url = "https://example.com/";
translate.key = process.env.TRANSLATE_KEY;
// or
const lTranslate = Translate({
engine: "libre",
url: "...",
key: "YOUR-KEY-HERE",
});
This library uses promises which need to be awaited for the translated result:
// Browser; jQuery for demonstration purposes
$("#translate").submit(async (e) => {
e.preventDefault();
const text = $(".text").text();
const spanish = await translate(text, { to: "es" });
alert(spanish);
});
// Node.js; serverjs.io example for demonstration purposes
const route = async (ctx) => {
const spanish = await translate(ctx.body, { to: "es" });
return send(spanish);
};
Current package and development: Francisco Presencia
Original package and idea: Andrew Lunny (alunny), Marak Squires, Google
Testing in Internet Explorer supported by BrowserStack:
FAQs
Translate text to different languages on node.js and the browser
The npm package translate receives a total of 10,683 weekly downloads. As such, translate popularity was classified as popular.
We found that translate demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
We're excited to announce that Socket now supports the Java programming language.
Security News
Socket detected a malicious Python package impersonating a popular browser cookie library to steal passwords, screenshots, webcam images, and Discord tokens.
Security News
Deno 2.0 is now available with enhanced package management, full Node.js and npm compatibility, improved performance, and support for major JavaScript frameworks.