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

@awes-io/nuxt-localization

v0.13.26

Published

Admin panel for editing translations.

Downloads

745

Readme

Awes.io Module for Editing Translations

This module is an interface, that helps you to edit translations in your database.

Basic usage

  1. Make shure, you are using @awes-io/ui and @nuxtjs/axios
  2. Install the module yarn add @awes-io/nuxt-localization
  3. The frontend part is ready!

Backend endpoint

By default, the module will make next requests to you backend

Fetch translations to edit

// GET /api/translations/edit?page={page}&limit={limit}&search={search}

// Expected response
{
    "data": [
        // array of translations: id, name and value
        {
            "id": 1,
            "name": "ui.hello",
            "value": {
                "en": "Hello",
                "de": "Hallo"
            }
        },
        {
            "id": 1,
            "name": "another.translation.key",
            "value": {
                "en": "Another translation key"
                // locales may be missing
            }
        }
        // ...
    ],
    "meta": {
        "current_page": 1, // required
        "per_page": 15, // required
        "total": 42 // required
        // ...
    }
}

Add new translation

// POST /api/translations/edit

// Request body
{
    "name": "ui.hello",
    "value": {
        "en": "Hello",
        "de": "Hallo"
        // ... other languages in current project
    }
}

// Expected response - status 200

// Error response - status !== 200

{
    "errors": {
        "name": "Key already exists",
        "value.en": "Default translation is required"
    }
}

Save edited translation

// PATCH /api/translations/edit/{id}

// Request body
{
    "id": 1,
    "name": "ui.hello",
    "value": {
        "en": "Hello",
        "de": "Hallo",
        "ru": "Привет"
    }
}

// Expected response - status 200

Delete translation

// DELETE /api/translations/edit/{id}

// Expected response - status 200

Configuration

// nuxt.config.js

{
    awesIo: {
        nuxtLocalization: {
            // the localization base route, attached to project
            route: '/localization',

            // backend endpoint
            endpoint: '/api/translations/edit',

            // link to download translations (hidden by default)
            export: '',

            // if string is longer, then this limit it will be rendered as textarea
            textLimit: 128,

            // name of data field in response
            data: {
                default: {},
                response: 'data'
            },

            // name of errors field in response
            errors: {
                default: {},
                response: 'errors'
            },

            // pagination request params and response field names
            pagination: {
                page: {
                    default: 1,
                    request: 'page',
                    response: 'meta.current_page'
                },
                limit: {
                    default: 15,
                    request: 'limit',
                    response: 'meta.per_page'
                },
                total: {
                    response: 'meta.total'
                }
            },

            // search request params
            search: { request: 'search' }
        }
    }
}

Ensure to write proper commit message according to Git Commit convention