Wappler Version: 5.5.3
Operating System: Windows and Ubuntu (Linux)
Server Model: NodeJS
Database Type: Postgres
Hosting Type: Docker
Expected behavior
Custom App connect Module feature should have worked properly for Docker Deployments, but doesn't
Actual behavior
Wappler fails to create the links for the custom app module created using the extesnions feature in project settings
How to reproduce
- Create a new project with a target Server type as Docker
- In project settings add a new custom app module, select a folder, hit save
- Populate the componenets.hjson created in the folder
- refresh the app drawer, you would notice that your newly created custom app modules is not visible in the drawer
Further Details:
When we create a new app connect extension from Project settings, e.g.: mapping to folder say “extensions”, the below line gets added to the project.json file located in .wappler folder.
"extensions": [
{
"name": "file:extensions"
}
]
it then creates the app_connect/components.hjson and app_connect/package.json files in the extensions folder.
a shortcut/link gets created in node_modules folder which points to your chosen extension folder which in this case is “extensions”.
So basically when Wappler App connect module load-up in the Modules drawer, they pickup the extensions array from the project.json, and then fetch the modules using the shortcut/link, which basically points to node_modules/extensions folder.
In case of npm repo installed, it pulls them directly from node_modules
Now the issue:
In a Docker Deployment, there is no node_modules folder created on the host machine, so basically when you add a new extension or fetch from npm/github repo, it does all of the above but in the Container environment, as the docker-compose holds no volume mapping for the node_modules, it fails to render the module in the UI, as the wappler UI is operating on the host machine.