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

@connectedcars/crowdin-integration

v0.1.5

Published

Tools for managing uploading and fetching translations to Crowdin

Downloads

718

Readme

crowdin-integration

Common setup for fetching and updating translations using the crowdin API.

Usage

Config should go into crowdin.json. See the example file here.

On the Crowdin, go to your project -> content -> settings on the .pot file. In Resulting file after translations export, the value should be /locales/%two_letters_code%.po to get a consistent path to use. Alternatively put a languageMap in the crowdin.json setting file, mapping the language codes to the desired output.

Add the two supplied scripts to your package file:

    "upload-translations": "upload-translations",
    "fetch-translations": "fetch-translations",

upload-translations uploads the template.pot located in the configured workingDir and updates crowdin to use it.

fetch-translations downloads a zip file containing the .po files. The files are extracted and moved to the working directory. Optionally a pull request is created, featuring a more readable diff, making it easier to quickly validate the actual translation changes.

Settings overview:

| Setting | Description | Sample value | | --- | --- | --- | | project | The crowdin 'project name'. | connectedcars-mobileapp | | projectId | The crowdin 'project id'. Can be found on the project home page under details. | 306911 | | CROWDIN_API_TOKEN | Personal Access Token from Crowdin. Prefereably use as env var. | b0088e9f... | | workingDir | The local directory in the project where the .po and .pot files are. | locales | | remotePath | The full remote path | /develop/locales/template.pot | | extractPath | The path inside the zip file crowdin provides. | develop/locales | | supportedLanguages | A list of the languages to extract. | [ "da", "de", "sv", "es", "fi", "fr" ] | | languageMap | Map languages to a different format. | { "da-DK": "da" } | | pullRequest | Optional settings for creating an automatic pull request. | { "githubProject": "connectedcars/mobile-app", "baseBranch": "develop" } | | force | Force pull request creation or source upload when outside basebranch. Prefereably use as argument: --force | { "githubProject": "connectedcars/mobile-app", "baseBranch": "develop" } |