How to update nodemon for Wappler

Wappler General Need Help
1

I’m slogging through learning to use Wappler effectively and keep stumbling over things, likely because there are things I don’t even know where to look for solutions.

Updating to the updated nodemon is my current challenge.

I’m getting messages in Wappler informing me that there’s a new version of nodemon available. It tells me that I’m running version 2.0.22 and that the latest version is 3.01 . . . what it doesn’t tell me is where to go and how to install the update.

I’m sure there’s no end to the number of people for whom this is basic child’s play. While I’d like to be one of those people, I have some distance to go.

So, is there anyone tickling the keyboard who can enlighten me just a wee bit today?

Thank you very much in advance for anything you can do to help!

2

From the bottom toolbar you can simply run “Update Node Packages” and that will update all the outdated modules like nodemon.

image

3

George —

Thank you for getting back to me. I think I see the problem I’m having . . . my bottom toolbar does not have the option you are pointing me to:

image
image1174×27 19.3 KB

How do I get my toolbar to match what yours is showing?

Thank you for your time and kind assistance with this.

     Norman
4

Hi Norman,

The difference is due to the Server Type under the Project Target settings. Your development target is running with Wappler Local Server (shown as Local Web Server in the bottom status bar) as the Server Type and George’s screenshot is shown when Docker is selected as the Server Type.

My understanding is that when Wappler Local Server is selected as the Server Type, then it is running the node application on the NodeJS version installed on the local computer rather than creating a package.json file required to run in a docker environment.

5

Ah I see what you mean. You are using the build in Wappler Local Server. Yes we will be updating those modules shortly as well. So you can ignore the message for the nodemon update available for now and it will go away on on the next Wappler update.

6

Well . . . I guess it’s time that I start over again with my first project and figure out how to use it with Docker instead of the Wappler Local Server.

I apparently didn’t get it right on the first (vertical learning curve) attempt. Maybe I will on the second.

7

Well local server should be all fine to use and eastbound start with as well do more local development. You can use docker for the remote deployment or for more complex local development as well.