> remove-json-keys
Simply remove JSON keys via CLI command.
Installation
pip install remove-json-keys
Usage
Run the CLI:
remove-json-keys [options] # or removejson
If no options are passed, the CLI will:
- Prompt for keys to delete
- Auto-discover closest child
json_dir - Delete keys from found JSON files
Note: Key/values can span multiple lines and have any amount of whitespace between symbols.
Options
Options can be set by using command-line arguments:
| Option | Description | Example |
|---|---|---|
-d, --json-dir |
Name of the folder containing JSON files (default: _locales) |
--json-dir=data |
-k, --keys |
Comma-separated list of keys to remove | --keys=app_DESC,err_NOT_FOUND |
--config |
Use custom config file | --config=path/to/file |
init, -i, --init |
Create .remove-json.config.json5 in project root to store default settings | |
-n, --no-wizard |
Skip interactive prompts during start-up | |
-h, --help |
Show help screen | |
-v, --version |
Show version | |
-V, --debug [target_config_key] |
Show debug logs | |
--docs |
Open docs URL |
Examples
Remove author key from JSON files found in default _locales dir:
remove-json-keys --keys=author # prompts for more keys to remove
Remove info_SUCCESS key from JSON files found in messages dir:
remove-json-keys -n --keys=err_NOT_FOUND --json-dir=messages # no prompts
Remove app_DESC + app_VER keys from JSON files found in data dir:
remove-json -n -k app_DESC,app_VER -d data # no prompts
Config file
Run remove-json -- init to create .remove-json.config.json5 in your project root to set default options.
Example defaults:
{
"json_dir": "_locales", // name of the folder containing JSON files
"keys": "", // keys to remove (e.g. "app_NAME,author")
"force": false, // force overwrite existing config file when using --init
"no_wizard": false // skip interactive prompts during start-up
}
Note: CLI arguments always override config file.
MIT License
Copyright © 2023–2026 Adam Lui.
Related
🌍 translate-messages - Translate en/messages.json (chrome.i18n format) to 100+ locales automatically.
🏷️ project-markers - Common project root markers.
Metadata
Release files for remove-json-keys 1.10.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| remove_json_keys-1.10.2.tar.gz | 18.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| remove_json_keys-1.10.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.9 kB
Release files / remove_json_keys-1.10.2.tar.gz
| Download URL | remove_json_keys-1.10.2.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c2965b1b964cf61ec755e11d83a66f59588cbb5e715b50907407ab522b15224
|
|
BLAKE2b-256 checksum How to use checksums |
af076270fd0b0f2cd946efb31e8161fd827434d76b94e041c845d10eb86d15b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency logRelease files / remove_json_keys-1.10.2-py3-none-any.whl
| Download URL | remove_json_keys-1.10.2-py3-none-any.whl |
|---|---|
| Size | 21.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d82b6de1b58dcabc24b51e7c3827b707570b9511b4f60318fef43f4b23c3d782
|
|
BLAKE2b-256 checksum How to use checksums |
79a731dbfe414f7196dad38a687f4f5cccaff1430934ac91cb670f4ea032472e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 6, 2026.
Transparency log