# cryptx/4.2.1/package.json

CryptX, version 4.2.1. 21 lines.

- Page: https://pluginprobe.com/plugins/cryptx/4.2.1/code/package.json
- Raw: https://pluginprobe.com/plugins/cryptx/4.2.1/raw/package.json
- Modified: 2026-09-11T17:18:18+00:00

Line numbers below start at 1. Link to a line or a range by appending a fragment to the
page URL, for example `https://pluginprobe.com/plugins/cryptx/4.2.1/code/package.json#L10-L20`.

```json
{
  "name": "cryptx",
  "version": "4.2.1",
  "description": "Build setup for the CryptX settings screen and the editor block. React and the component library come from WordPress itself, so only this plugin's own code is bundled.",
  "private": true,
  "license": "GPL-2.0-or-later",
  "comments": {
    "entry-points": "Both entry points are named on purpose. wp-scripts scans src/ for block.json files, and as soon as it finds one it uses ONLY the entry points it derives from them -- the default src/index.js is dropped without a word. Adding the block that way would have shipped a release whose settings screen renders nothing. Naming them explicitly wins over the scan (see getWebpackEntryPoints in @wordpress/scripts). The 'block/index' name is what puts the result next to the block.json copied to build/block/, which is the directory register_block_type() is pointed at."
  },
  "scripts": {
    "build": "wp-scripts build index=src/index.js block/index=src/block/index.js",
    "start": "wp-scripts start index=src/index.js block/index=src/block/index.js",
    "lint:js": "wp-scripts lint-js src",
    "test:e2e": "node tests/e2e/dynamic-navigation.mjs"
  },
  "devDependencies": {
    "@wordpress/scripts": "^34.1.0",
    "playwright": "^1.62.1"
  }
}

```