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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@penskemediacorp/wordpress-scripts

v2.0.0

Published

This repository hosts a collection of scripts designed to enhance your experience and efficiency when working with the PMC WordPress site. This package builds upon and extends the capabilities of the official @wordpress/scripts package, providing addition

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

asannadasannadhvonghvongvtellavtellapmc-machine-userpmc-machine-usercmatteiscmatteisnkimnkimvsharma-pmcvsharma-pmc

Keywords

Readme

PMC WordPress Scripts

This repository hosts a collection of scripts designed to enhance your experience and efficiency when working with the PMC WordPress site. This package builds upon and extends the capabilities of the official @wordpress/scripts package, providing additional tools and functionalities tailored specifically for the PMC WordPress environment.

Features

  • Streamlined Workflows: Simplify the process of theme and plugin development with workflows tailored for efficiency.

  • Automation Scripts: Utilize custom scripts to automate repetitive tasks, saving time and reducing errors.

  • Enhanced WordPress Scripts: Benefit from enhancements to standard WordPress scripts that offer increased functionality and improved productivity.

  • TypeScript Support: Incorporate TypeScript into your development with enforced coding standards and type-checking, ensuring cleaner and more robust code.

Installation

Follow these steps to seamlessly incorporate the scripts into your WordPress project:

  1. Install npm: Ensure that npm is installed on your system. If it is not installed, download and install it from the official npm website.

  2. Install the PMC WordPress Scripts Package: Open your terminal, navigate to the root of your project, and execute the following commands:

    nvm install 20
npm install @penskemediacorp/wordpress-scripts --save-dev

  3. Commit Necessary Files: After installation, commit the tsconfig.json, package.json, and package-lock.json files to your project repository.

By following these steps, the scripts will be added to the devDependencies section of your project, enabling their use within your development workflow.

Project Folder Structure

The project main entries files should be placed under src folder.
The generated files will be placed under build folder.

  • build/ (generated by the build script)
    • main-entry1.js
    • main-entry1.asset.php
    • main-entryX.js
    • main-entryX.asset.php
    • ...
  • src/ (individual entry file under this folder will be generated in build folder)
    • __tests__/
      • main-entry1.test.ts
      • main-entryX.test.ts
      • ...
    • modules/
      • __tests__/
        • module1.test.ts
        • ...
      • module1.ts
      • ...
    • folderX/
      • ...
    • main-entry1.ts
    • main-entryX.ts
    • ...

Usage

Contributing

The scripts block in package.json is hand-maintained

The scripts block in this package's own package.json is hand-maintained — in particular the postinstall hook (pmc-scripts sync) is what wires this wrapper into a consuming project.

That same hook used to be a footgun: running npm install (or npm run packages-update, which installs under the hood) fired pmc-scripts sync against this repo itself, rewriting its own scripts block with the defaults meant for consumers. This is now prevented in code — updateProjectPackageJson() / updateProjectTsConfigJson() in utils/config.js bail out via isSelf() when the sync target resolves to this package's own package.json, so the sync only ever mutates a consuming project. See test/config.test.js.

If you ever do see a diff touching the scripts block (e.g. from a future tooling change), revert only that block to its committed state — do not blanket-revert the whole file (e.g. git restore package.json), since that would also discard any legitimate dependency-version updates you want to keep.

License