NodeJS problems when refusing to update modules

If you refuse to update the nodejs modules in the Wappler (the message appears only once):
18

The nodejs module controls disappear from the Wappler interface and the project has a problem with the local server:

Question: how can I fix the local server and restore the interface elements in the project?

Seems to me like you have selected a target that doesn’t have NodeJS as server model selected.

The situation is like this. I updated the Wappler. After the update, it automatically opened the project and suggested installing new NodeJS packages. I was thinking about something and I refused. After that, this project lost the nodejs package management interface in the Wappler. And the local target has also disappeared. The local target has disappeared even from the list of available targets. Only the target on the VDS server remains.

This only happens if you opt out of the update. How do I return the update Wappler message or update the NodeJS packages in a different way?

The problem was solved only by removing the project from the list of available projects. And then re-opening it through the project folder:
19

In this case, the Wappler re-shows the modal window with the NodeJS package update. After the update, the local server resumes stable operation and the missing interface elements appear.

It would be great if the modal window for updating modules could be called more easily, in the event that a refuse was made at the first notification for some reason.

Well usually it’s doesn’t matter, if you are on a NodeJS target the toolbar should show and even if you refuse to install, you can click on the toolbar to install the node packages later on.

But maybe we should require the package update always as it is required otherwise the NodeJS server might not start due to the missing packages

1 Like