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

poeditor-tool

v0.0.3

Published

JavaScript cient for POEditor translations solution

Downloads

5

Readme

poeditor-client

JavaScript client for POEditor translations solution.

This is a placeholder module. Functionality will be added continually. You can expect it to be fully functional in version 0.1.0.

Installation

poeditor-client is an NPM module. To install please run

npm install poeditor-client

Usage

poeditor-client allows you to access POEditor's API from your JavaScript code. For now there is no CLI tooling, you have to use it as a JavaScript module.

Getting started

You have to obtain your POEditor API access key. Please see POEditor docs on authentication to find out how.

This module exports a class, POEditorClient, that you need to instantiate to access all other API operations:

var POEditorClient = require('poeditor-client');
var client = new POEditorClient('<YOUR API ACCESS TOKEN HERE>');

Following sections will assume you have this client variable available in your code.

This module exposes promise-based API.

Working with projects

At the heart of POEditor API there's project. You can list and add projects through client.projects object.

Listing projects

To list all the projects use client.projects.list() method:

client.projects.list().then(function(projects) {
	// projects is an array of Project objects
	// see below for what can you do with a Project object
});

Adding a project

To add an empty project use client.projects.add() method. This method accepts an object with name and (optional) description keys:

var definition = { name: 'My project', description: 'Truly amazing POEditor project' };			
client.projects.add(definition).then(function(project) {
	// project is an instance of Project class
	// see below for what can you do with this project object
});

Working with project languages

In order for POEditor project to be functional it needs to have one or more languages attached.

Note In following code examples I will assume there is a project variable that represents a single POEditor project. See how you can obtain this object above.

You can manipulate with project languages using project.languages object.

Listing project languages

To list all project languages use project.languages.list() method:

project.languages.list().then(function(languages) {
	// languages is an array of Language objects
	// see below for what can you do with a Language object
});

Adding a language

To add a language to your project use project.languages.add() method. This method accepts an string parameter - a language code:

project.languages.add('de-at').then(function() {
	// Yaaaay! You just added an Austrian variant
	// of German language to your project!
});

Deleting a language

To remove particular language from your project use project.languages.delete() method. This method accepts an string parameter - a language code:

project.languages.delete('de-at').then(function() {
	// Well maybe you didn't like Austrian German that much in the end...
});

Setting a reference language

You can set a language to act as a reference language for your project. To do this, two methods are available on project.languages object: setReferenceLanguage() and unsetReferenceLanguage(). They both accept a language code as a parameter:

project.languages.setReferenceLanguage('de-at').then(function() {
	// Austrian German is now your reference language
});

project.languages.unsetReferenceLanguage('de-at').then(function() {
	// Maybe Austrian German was not what you wanted
});

You can perform these operations on Language objects too, using setAsreference() and unsetAsReference() methods (assuming that you have obtained a language object):

language.setAsReference().then(function() {
	// The language is now a reference language
});

language.unsetAsReference().then(function() {
	// The language is not a reference language anymore
});

Working with project terms

The basic building block of POEditor projects are terms.

If you are not interested in translations of terms for a specific language, you can use project.terms object to list, add or comment on terms.

If you need both terms and translations, you have to use language.terms object.

Following guide applies to both of these objects, I will assume termsObject variable refers to either of forementioned objects.

Listing project terms

In order to obtain a list of project terms you need to use list() method:

termsObject.list().then(function(terms) {
	// Terms is an array of Term objects
	// See below for what you can do with Term objects
});

Adding a term (or an array of terms)

You can add one or more terms at once using add() method:

termsObject.add(definition).then(function(result) {

});

termsObject.add(arrayOfDefinitions).then(function(result) {

});

You can pass either an object with term definition (see below) or an array of these objects. This method returns a promise that resoves with an object containing two keys - added is a number of terms that were added (excluding terms that already existed in the project), parsed is the number of terms you provided.

Each term definition object should have the following structure :

{
	string term,
	[string plural],
	[string comment],
	[string context],
	[string reference],
	[array<string> tags]
}

Deleting a term (or an array of terms)

You can add one or more terms at once using delete() method:

termsObject.delete(definition).then(function(result) {

});

termsObject.delete(arrayOfDefinitions).then(function(result) {

});

You can pass either an object with term definition or an array of these objects. This method returns a promise that resoves with an object containing two keys - deleted is a number of terms that were deleted, parsed is the number of terms you provided.

Commenting on a term (or an array of terms)

You can add one or more terms at once using comment() method:

termsObject.comment(definition).then(function(result) {

});

termsObject.comment(arrayOfDefinitions).then(function(result) {

});

You can pass either an object with term definition or an array of these objects. This method returns a promise that resoves with an object containing two keys - added is a number of terms that were commented on, parsed is the number of terms you provided.

Exporting project terms

You can export project terms to file(s) using project.export() method on single project object:

// Check POEditor API reference for more info on export options
var options = {
	type: 'po',
	tags: ['cool feature'],
	filters: ['translated', 'not_fuzzy']
};

project.export(options).then(function(fileNames) {
	// fileNames is an array of exported file URLs
});

This method exports all project languages. In case you only want to export a single language, you have to obtain a single language object. See how to do that here.

You can then use language.export() method to export a single language:

// Options are the same as above
project.export(options).then(function(fileName) {
	// fileName is exported file URL
});

Working with available languages

POEditor API provides a way of listing all available languages. You can then use this list to add languages to your projects.

This API is accessible via client.languages object.

Listing available languages

To list all available languages use client.languages.list() method:

client.languages.list().then(function(languages) {
	// languages is an array of objects with name and code property
});

Returned array will contain plain JavaScript objects with name (human readable name) and code properties.