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

@freave/make-pot

v0.0.16

Published

Scans files in a given directory for translatable strings. Generates a POT file.

Downloads

17

Readme

Getting Started

Installation

Install with npm:

npm install --save-dev @freave/make-pot

Install with yarn:

yarn add @freave/make-pot --dev

Usage

make-pot --source path/to/input/folder --destination path/to/output/folder --domain domain

CLI options

make-pot --help output:

make-pot <args>

Options:
  --help         Show help                                                      [boolean]
  --version      Show version number                                            [boolean]
  --source       Space-seperated list of directories that should be searched.   [array] [required]
  --destination  Directory where the POT file will be placed.                   [string] [required]
  --domain       The domain that will be used inside the POT file.              [string] [required]
  --headers      The headers that will be added to the POT file.                [string]
                 Example: --headers.Language-Team Acme                        

Examples:

make-pot --source app resources --destination resources/lang --domain freave --headers.Report-Msgid-Bugs-To [email protected] --headers.Language-Team Acme

This will look for files in the app and resources directories and will create a POT file in the resources/lang directory with the domain freave and the headers Report-Msgid-Bugs-To and Language-Team Acme changed.

Roadmap

  • [x] PHP support
  • [x] Blade support
  • [x] Support all WordPress translation functions
  • [x] POT file header is customizable
  • [ ] Read info from style.css
  • [ ] Option to select output type (POT or JSON)
  • [ ] JSON / JS support

See the open issues for a full list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement".

Before you start

Make sure all commits are signed and marked as "verified". This is a requirement for merging pull requests. You can find instructions for signing commits here.

How to contribute

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Credits

Mike van Egmond - egmond.dev - [email protected] Freave B.V. - Freave.com - [email protected]