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

@popup-maker/extension-build-tools

v1.2.2

Published

Shared webpack and release tooling for Popup Maker standalone extensions.

Downloads

973

Readme

@popup-maker/extension-build-tools

Shared build tooling for Popup Maker standalone extensions (Pro-tier core addons).

Webpack preset

// webpack.config.js
const { createExtensionWebpackConfig } = require( '@popup-maker/extension-build-tools/webpack' );

module.exports = createExtensionWebpackConfig( {
	slug: 'popup-maker-exit-intent-popups',
	libraryGlobal: 'popupMakerExitIntentPopups',
	packageScope: '@popup-maker-exit-intent-popups',
	packages: {
		frontend: 'packages/frontend',
	},
	devServerPort: 8890,
} );

Options

| Option | Required | Description | |--------|----------|-------------| | slug | Yes | Plugin folder name under wp-content/plugins/. | | libraryGlobal | Yes | Window global root (e.g. popupMakerExitIntentPopups). | | packages | Yes | Webpack entries: { entryName: 'packages/…' }. | | packageScope | No | NPM scope for resolve aliases. | | publicPath | No | Defaults to /wp-content/plugins/{slug}/dist/. | | devServerPort | No | Enables devServer when set. | | copyPatterns | No | CopyWebpackPlugin patterns. | | dependencyExtractionPlugin | No | Override DEWP class (default: core plugin). |

Release CLI

{
  "scripts": {
    "release": "extension-build-release"
  }
}

Runs composer production install, webpack build, language pack compilation (POT → PO merge → MO + JSON), copies package.json files whitelist, and creates a versioned zip.

Ensure languages/**/* is in the files array so PO/MO/JSON ship in the zip.

i18n (Potomatic + langpacks)

Release automation (default)

extension-build-release calls extension-build-i18n --skip-translate before zipping:

  1. Regenerate .pot from PHP + package source
  2. Merge new strings into committed .po files (wp i18n update-po)
  3. Compile .mo (PHP) and .json (JS) files

Potomatic is not run during release by default — release packages whatever translations are already in languages/.

prepare-release also refreshes langpacks (without translate) so POT/MO/JSON land in the release commit.

Ongoing translation (develop branch)

  1. config/dictionaries/dictionary.json — brand terms Potomatic should not translate.
  2. .github/workflows/translate.yml — Potomatic on develop + manual dispatch; commits updated .po/.json files.

Default languages (15): es_ES,pt_BR,fr_FR,de_DE,ja,ru_RU,it_IT,nl_NL,pl_PL,tr_TR,id_ID,zh_CN,ar,sv_SE,ko_KR

Repo secrets: OPENAI_API_KEY (or Gemini/Anthropic). Optional vars: DEFAULT_TRANSLATION_LANGUAGES, DEFAULT_TRANSLATION_MAX_COST.

Override per extension in package.json:

{
  "extensionRelease": {
    "i18n": {
      "languages": "es_ES,pt_BR,fr_FR,de_DE,ja,ru_RU,it_IT,nl_NL,pl_PL,tr_TR,id_ID,zh_CN,ar,sv_SE,ko_KR"
    }
  }
}

Local commands

{
  "scripts": {
    "i18n:build": "extension-build-i18n --skip-translate",
    "i18n:pot": "wp i18n make-pot . languages/{text-domain}.pot --domain={text-domain} --exclude=vendor,vendor-prefixed,node_modules,tests,dist",
    "i18n:update": "wp i18n update-po languages/{text-domain}.pot languages/",
    "i18n:mo": "wp i18n make-mo languages/",
    "i18n:json": "wp i18n make-json languages/ --no-purge",
    "i18n:translate:dry-run": "extension-run-potomatic --dry-run --max-strings-per-job 10",
    "i18n:translate": "extension-run-potomatic"
  }
}

Quick local test: ./custom-tools/test-extension-i18n.sh wp-content/plugins/popup-maker-exit-intent-popups--modernize-v2 fr_FR

Force Potomatic during a release build: EXTENSION_I18N_TRANSLATE=1 pnpm run release

Skip langpack step: pnpm run release -- --skip-i18n

GitHub secrets & variables

Copy .env.secrets.example.env.secrets (gitignored), fill in values, then:

{
  "scripts": {
    "secrets:sync": "extension-sync-repo-secrets"
  }
}
pnpm run secrets:sync
# or target another repo:
GITHUB_REPO=PopupMaker/Exit-Intent pnpm run secrets:sync

Uses # --- Secrets --- / # --- Variables --- section headers in .env.secrets to route keys to encrypted secrets vs repo variables. Requires GitHub CLI (gh auth login).