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

vue3-i18n-sfc

v1.0.0

Published

Collects SFC i18n's and makes them translatable with one file

Downloads

18

Readme

vue3-i18n-sfc

The translation team (not developers) wants a file with all the keys to translate. But I love to use translations in Single File Components.

And I found a solution to make everyone happy: vue3-i18n-sfc export|import

Vue I18n Service makes to manage SFC translations easier in a file. It collects all the <i18n> definitions in Single File Components and collects them into a file.

What's the flow:

Hello.vue

<template>
  <div>{{ hello }}</div>
</template>

<i18n>
{
  "en": {
    "hello": "Hi 🙁"
  },
  "tr": {
    "hello": "Selam"
  }
}
</i18n>

⬇️npx vue3-i18n-sfc export > translations.json

{
  "src/components/Hello.vue": {
    "en": {
      "hello": "Hi 🙁"
    },
    "tr": {
      "hello": "Selam"
    }
  }
}

✏️translations.edited.json

{
  "src/components/Hello.vue": {
    "en": {
      "hello": "Hello 🙂"
    },
    "tr": {
      "hello": "Merhaba"
    }
  }
}

Editing translations.json using Web UI

Open https://edisdev.github.io/vue-i18n-translator/ and drop translations.json file which you've just generated. It will parse it and generate an useful interface to translate.

vue-i18n-translator

⬇️npx vue3-i18n-sfc import < translations.edited.json

updating file src/components/Hello.vue
<template>
  <div>{{ hello }}</div>
</template>

<i18n>
{
  "en": {
    "hello": "Hello 🙂"
  },
  "tr": {
    "hello": "Merhaba"
  }
}
</i18n>

And all is OK. Doesn't matter how many files you have, it simply distributes without any problem and any conflict.

Exporting i18n's in SFCs

This will generate a translations.json file (or whatever you named).

npx vue3-i18n-sfc export > translations.json

It has a simple format:

{
  "<file path>": {
    "<locale>": {
      "<key>": "<value>"
    }
  }
}

Here is an example:

{
  "src/components/Hello.vue": {
    "en": {
      "hello": "Hello"
    },
    "tr": {
      "hello": "Merhaba"
    }
  },
  "src/views/World.vue": {
    "en": {
      "world": "World"
    },
    "tr": {
      "world": "Dünya"
    }
  }
}

--dir

By default, vue3-i18n-sfc looks for SFCs in the src/ directory, if your components are in another directory, specify it by passing the --dir flag:

npx vue3-i18n-sfc export --dir=client/ > translations.json

--yaml

By default, vue3-i18n-sfc exports and imports files as json, if you want to use yaml, specify it by passing the --yaml flag:

npx vue3-i18n-sfc export --yaml > translations.yaml

Importing translations.json file to the SFCs

After bulk changing files, you can distribute import all the files calling import command.

npx vue3-i18n-sfc import < translations.json

This will update .vue files and replace them with changes.

Contributors

License

MIT.