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

sync-wp-manifest

v0.2.0

Published

Sync package metadata (package.json) to wordpress plugin entry file

Downloads

3

Readme

sync-wp-manifest

Sync package metadata (package.json) to wordpress plugin entry file

Installation

With node.js installed, use npm to install this package:

npm install sync-wp-manifest

Usage

You can run this package as a standalone executable or use it in a node.js script.

From the command line

sync-wp-manifest ./my-plugin/my-plugin.php ./my-plugin/package.json

Run sync-wp-manifest --help to view all available options

node.js API

import { replaceCommentInFile } from 'sync-wp-manifest';

replaceCommentInFile('./my-plugin/my-plugin.php', { version: '1.2.3' })
  .then(() => console.log('Done'))
  .catch((error) => {
    console.error(error);
    process.exitCode = 1;
  });

Result:

<?php
/**
 * Version: 1.2.3
 */
?>

you can also use custom transformations:

replaceCommentInFile('./my-plugin/my-plugin.php', { version: '1.2.3', description: 'My plugin is cool' }, {
  transform(
    name, // The name, as'Version'
    value, // '1.2.3'
    key // 'version'
    ) {
    // Return the resulting name and value as an array
    if (key === 'version') return [name, `${value}-alpha`];

    // ...or return null or undefined to use default transformation
    return undefined;
  }
})
  .then(() => ...)

Result:

<?php
/**
 * Version: 1.2.3-alpha
 * Description: My plugin is cool
 */
?>

Default transforms

By default, this package applies the following transformations to the input data:

  • Rename the name property to Plugin Name and capitalizes it's value, while removing the package scope, as well as the words plugin, wordpress and wp

    Input:

    {
      "name": "@my-company/extra-cool-wordpress-plugin"
    }

    Output:

    <?php
    /**
     * Plugin Name: Extra Cool
     */
    ?>
  • Replace UNLICENSED inside the license property to proprietary

Use a custom transformer to disable any of these transformations

Override values

You can use the wpPlugin property inside your manifest to override any values:

Input:

{
  "description": "This description is for internal use only",
  "wpPlugin": {
    "Description": "The public plugin description"
  }
}

Output:

<?php
/**
 * Description: The public plugin description
 */
?>

Note that values and keys inside wpPlugins will not be transformed, wo you have to pass the exact name of the property (eg Description, Plugin Name) instead of the keys used in package.json otherwise (description, name) respectively.