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

confluence-i18n-importer

v1.1.0

Published

Import translations from Confluence

Downloads

235

Readme

confluence-i18n-importer

Information

CLI tool to parse a Confluence page with a table containing translations to JSON files that can be used with i18next.

A blog article explaining how and why we use this tool at AppFoundry can be found on our blog.

Confluence table structure example:

table image

Any column not named TechnicalId, PageName or Image will be seen as a language.

Install: $ npm install -g confluence-i18n-importer

Example usage: $ confluence-i18n-importer -d CONFLUENCE_BASE_URL -i PAGE_ID -u USERNAME -p PASSWORD -o "/Users/john/Projects/xxxx/translations"

The i18n files are outputted by default in the directory where the command is ran from when the output flag is not given.

Options

| Flag | Description | | :-------------: |------------- | | -d | Domain of the Confluence page. Example 'https://confluence.yourcompany.com' | | -i | Page id of the confluence page to be parsed. If you want the page ID, go to Tools —> Page Information on the particular page you are interested in. You should see the page (content) ID shown in the URL when you do this. | | -u | The username of the confluence account. | | -p | Password or API token of the confluence account. API tokens are only avaiable on cloud hosted Atlassasian stacks. | | -t | When this flag is given the output files will have the TypeScript (.ts) extension. | | -o | Output directory for i18n files. Remeber to quote the path if there's spaces in the path. The directory already has to exist. Default the directory when the command is ran from. | | --noEmpty | Ignore translations with an empty value |

Atlassian Cloud usage

When using the Atlassian Cloud offering of Confluence (hosted on atlassian.net), you must provide an API token for authentication, instead of either your user's password or API token, and you must provide your email as your username. See https://developer.atlassian.com/cloud/confluence/basic-auth-for-rest-apis/ for more details.

Using locally

Install

$ npm install

Linking package

$ npm link

Using the package

$ npm run build && confluence-i18n-importer -d CONFLUENCE_BASE_URL -i PAGE_ID -u USERNAME -p PASSWORD

Example output

Files: en_US.js, fr_BE.js, nl_BE.js

export default {
  LoginTitle1: `Welcome back at`,
  LoginTitle2: `sign in to continue`,
  LoginButton: `Sign in`,
};