Wappler extension npm sync
Already added a wappler-* package in Wappler Project Settings → Extensions?
This wizard generates cp commands from node_modules into your project folders.
Run them from your Wappler project root after npm install.
Installing from GitHub instead? Use the Git Extension Installer (clone + copy, no npm required).
When to use this wizard
Use this if you installed via Wappler → Project Settings → Extensions and
Project Updater did not copy every file into your project. It generates
cp commands from node_modules using the same map as
wappler-install.json.
- Add the extension in Wappler Project Settings → Extensions.
- Run
npm installin your Wappler project root. - Try Project Updater → Update first.
- If anything is still missing, use this wizard to copy from
node_modules. - Quit Wappler completely and reopen.
- 1 Type
- 2 Extension
- 3 Commands
What are you copying?
Choose the Wappler layer. Pick Both for full-stack extensions (e.g. PuSH-IT, BeeGone, TipWap).
Which npm package?
Pick the extension you added in Wappler. Have a terminal open in your Wappler project root (folder with package.json).
Important: run these commands in the Wappler project where you added the extension
(folder with package.json). After npm install, confirm
node_modules/wappler-* exists before copying.
Your sync script
1 — Folders for this extension
Derived from the selected extension's wappler-install.json copy map — not a generic list.
2 — After copy
3 — Create folders and copy files
One script: mkdir -p for every destination folder, then cp from node_modules. Use Copy script below (step 1 is the same folders only).
Why this page exists
Optional fallback when Project Updater did not copy every file after an npm install.
This assistant uses the same wappler-install.json map as the Git installer — sources are under
node_modules instead of a clone.