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

gatsby-source-transifex

v1.0.0

Published

Gatsby source plugin for building websites using the Transifex CMS as a data source

Downloads

3

Readme

gatsby-source-transifex

Install

npm install --save gatsby-source-transifex

How to use

First, you need a way to pass environment variables to the build process, so secrets and other secured data aren't committed to source control. We recommend using [dotenv][dotenv] which will then expose environment variables. [Read more about dotenv and using environment variables here][envvars]. Then we can use these environment variables and configure our plugin.

Using Delivery API

// In your gatsby-config.js
module.exports = {
  plugins: [
    {
      resolve: `gatsby-source-transifex`,
      options: {
        organization: `your_organization`,
        project: `your_project`,
        source_lang_code: `en`, // default lang
        locales: [`de`,`sv`], // array of all translated lang
        auth: `${process.env.TRANSIFEX_USER}:${process.env.TRANSIFEX_TOKEN}`,
      },
    },
  ],
}

Query for all nodes

You might query for all of resources:

{
  allTransifexTranslationField {
    nodes {
      id
    }
  }
  allTransifexResourceField {
    nodes {
      id
    }
  }
}

Translation as JSON

{
  transifexTranslationField(id: {eq: "transifex-{insert-your-resource-id}-{insert-locale}"}) {
    id
    json
  }
}

Resource as JSON

{
  transifexResourceField(id: {eq: "transifex-{insert-your-resource-id}"}) {
    id
    json
  }
}

All Translations from locale

{
  allTransifexTranslationField(filter: { node_locale: { eq: "de" } }) {
    nodes {
      id
    }
  }
}