Install manifest builder
You are creating a small JSON file — wappler-install.json — that tells install tools
which files to copy where when someone adds your extension to a Wappler project.
Think of it as a machine-readable install section for your GitHub repo.
- 1 Identity
- 2 Layers
- 3 Copy map
- 4 Notes
- 5 Export
What you are building
A wappler-install.json file lives in your extension repo root (next to README.md). Install wizards read it and generate cp commands for the user. You still write a README for humans — this file is for tools.
Extension identity
Name and ID for your manifest. The ID slug should stay the same across versions (e.g. push-it, redirect-it).
Lowercase letters, numbers, and hyphens only.
Import existing JSON
Paste a wappler-install.json to edit it in this wizard.
Wappler layers
Does your extension ship Server Connect actions, App Connect UI, or both? This controls which copy tables you fill in next.
Copy map
List every file in your extension repo that must be copied into a Wappler project.
Source = path in your repo. Destination = path in the user’s Wappler project root (e.g. lib/modules/pushit.js) — relative only; install tools assume the user runs commands from that folder.
Type your module base name (e.g. redirectit), then click the button. We add the usual three copies: .hjson + .js in lib/modules/ and extensions/server_connect/modules/.
| Source (repo) | Destination (project) | Remove |
|---|
Folders to create (mkdir -p) are derived automatically from destination paths.
Post-install notes
What must the installer do after copying files? These appear as bullet points in install wizards — e.g. restart Wappler, set env vars, add a Browser component in the designer.
Preview & export
This is your finished wappler-install.json. Copy or download it, then follow the steps below.
Schema v1: JSON Schema · Extension Installer
Installing an extension?
Use the install assistant to generate git clone and cp commands from a manifest or the bundled catalog.