| @@ -1,15 +1,20 @@ | ||
| 1 | 1 | { |
| 2 | 2 | "name": "cryptx", |
| 3 | - "version": "4.1.1", | |
| 4 | - "description": "Build setup for the CryptX settings screen. React and the component library come from WordPress itself, so only this plugin's own code is bundled.", | |
| 3 | + "version": "4.2.1", | |
| 4 | + "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.", | |
| 5 | 5 | "private": true, |
| 6 | 6 | "license": "GPL-2.0-or-later", |
| 7 | + "comments": { | |
| 8 | + "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." | |
| 9 | + }, | |
| 7 | 10 | "scripts": { |
| 8 | - "build": "wp-scripts build", | |
| 9 | - "start": "wp-scripts start", | |
| 10 | - "lint:js": "wp-scripts lint-js src" | |
| 11 | + "build": "wp-scripts build index=src/index.js block/index=src/block/index.js", | |
| 12 | + "start": "wp-scripts start index=src/index.js block/index=src/block/index.js", | |
| 13 | + "lint:js": "wp-scripts lint-js src", | |
| 14 | + "test:e2e": "node tests/e2e/dynamic-navigation.mjs" | |
| 11 | 15 | }, |
| 12 | 16 | "devDependencies": { |
| 13 | - "@wordpress/scripts": "^34.1.0" | |
| 17 | + "@wordpress/scripts": "^34.1.0", | |
| 18 | + "playwright": "^1.62.1" | |
| 14 | 19 | } |
| 15 | 20 | } |
