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

etty-webpack-plugin

v0.2.0

Published

Etty translations autocompile plugin for webpack 4+

Downloads

4

Readme

Webpack 4+ plugin for generate etty translations

Usage

  1. Install
npm install etty-webpack-plugin
  1. Use in webpack.config.js
var EttyPlugin = require("etty-webpack-plugin").default
{
    // ...other configs
    plugins: [
        new EttyPlugin({
            // options here
        })
    ]
}

Options

Name | Type | Required | Default | Description ---- | ---- | -------- | ------- | ----------- template | string | yes | - | A path to the JSON template that you are using with etty locales | string | yes | - | A path to the JSON that contains locales array (string[]) that you are using with etty compileTo | string | yes | - | A path to the folder where to place generated translations prefillFrom | string | no | value of compileTo | A path to the folder where your existing translation files are placed logLevel | "all", "warning", "error", "none" | no | "all" | Log level of the plugin. "all" will show success, info, warning and error messages; "warning" - warning and error messages; "error" only error messages; "none" will not display any messages. minify | boolean | no | false | Whether to minify output JSON files or not.

Example

Assume we have this kind of the project structure:

src
|- config
|- |- locales.json
|- |- template.json
translations
webpack.config.js

We want our translations to be generated to the translations folder.
So. our locales.json

[ "en", "de", "ru" ]

and our template.json

{
    "Homepage": {
        "title": "",
        "description": ""
    }
}

Using etty-webpack-plugin in webpack.config.js:

var EttyPlugin = require("etty-webpack-plugin").default

{
    // ..other configs
    plugins: [
        new EttyPlugin({
            template: "./src/config/template.json",
            locales: "./src/config/locales.json",
            compileTo: "./translations"
        })
    ]
}

Running webpack will result placing to the translations folder three files:

src
|- config
|- |- locales.json
|- |- template.json
translations
|- de.json
|- en.json
|- ru.json
webpack.config.js

Sample content of en.json:

{
    "Homepage": {
        "title": "en:Homepage.title",
        "description": "en:Homepage.description"
    }
}

That's it!
More detailed and fully working in real life example you can find at etty-example repo :)

NOTE

Note, that if you want webpack to react on your template.json and locale.json changes, they obviously must be included into your application (i.e. imported somewhere of your application). If you are using etty, then this is not a problem for you, because you are probably already did it.

Contributin'

Any issues, feature and pull requests are highly appreciated. Feel free to criticize and advise.