Hello,
When deploying NodeJS projects via Docker, I get deprectaed warning messages for these Node packages.
rimraf@2.71.; glob@7.2.3; uuid@3.4.0; adal-node@0.2.4
Except, uuid (v10.0.0 in the package.json), none of the other appear in the package.json file. Can these packages be upgraded to the latest versions by users? Or do these changes need to be incorporated by the Wappler team?
When you deploy to docker, the script copies the local package.json file from your Wappler project folder onto docker. It then runs the npm install command to download and install those packages in docker.
So looks like the packages you have specified in package.json are out of date. This could just happen because they get deprecated / updated since you created the project originally.
Have you tried opening the project folder in your terminal and running npm update to update the packages? I'd backup the package.json and lock files first before running it in case the update installs a breaking change.
You can also just update the individual packages by running npm update <pkg-name>
Edit: the packages might not appear in package.json because it only lists the major packages your app needs - those major packages have dependancies on other packages again, which is what you're seeing. The full list of dependancies is stored in package-lock.json
Just curious, but when you click on the update button, does it not also install the dependancies too?
Hi Rene,
Thanks for the information, this is very useful to know.
I checked the package-lock.json after updating the node packages, and the versions of the deprecated packages (both main and dependencies) are still the same.
adal-node package is showing as deprecated in the package-lock.json and is suggesting to migrate to msal-node.
uuid v3.4.0 is suggesting to migrate to v7 or higher.
Hi guptast,
npm allows you to set update limit on packages and dependancies, so for example you might only allow minor version updates to a package, or major updates up to version X. Developers do this so major updates to dependancies don't break their packages and code.
You can have a look a bit more about this here: Understanding npm Versioning - DEV Community which shows the version options like ^ and ~.
I had a look at the adal-node package and can confirm it is deprecated, with the last version at 0.2.8.
Unfortunately that means you either have to keep using it as-is, or look at other options. An upgrade with meal-node will require some code to be to be rewritten in the parent package to support the change - so in short, sorry not great news and no easy fix.
I'm assuming these packages are as a result of some package or Wappler extension you've installed as I haven't seen the same error node warnings yet?
Hi Rene,
Thank you for providing further insights into how the packages and dependencies function in a Node project.
In the package-lock.json file, I can see that the adal-node package is a dependency for the tedious package (the node driver for MSSQL). The project is integrated with an MSSQL database.
As I don't have a comprehensive understanding of the inner workings and interdependencies of Node packages, I believe this task would be best handled by the Wappler team to ensure seamless integration of the updated packgae versions.
