DrewW
Mega Sage

I would make sure that you backup your project before you continue just incase things go badly.

So with the release of Paris I found that it does not like v17 of the Framework and that you need to upgrade to the latest version.  I thought this was a strait forward command of "npm update" but that did not work.  So off to do some searching and some reading.  I found this

https://www.carlrippon.com/upgrading-npm-dependencies/

Which was very helpful and found out that "npm update" only updates to the latest dot version of the ones that you have installed.  So to check what's is out of date you can run "npm outdated" and you should see something like this.

find_real_file.png

So as you can see there are a number of things that are not the latest version.  To update things in bulk you can do "npx npm-check-updates -u" and you should get something like this.

find_real_file.png

So as it says at the bottom you then need to do a "npm install".  Once that is done I did an "npm outdated" to make sure and found that not all of the packages updated.

find_real_file.png

So now what?  Well if you would like this updated also you will need to update them individually.  So now you need to do the following to update each package on its own.

npm install @servicenow/ui-renderer-snabbdom@latest

Or to do more than one at at time

npm install @servicenow/ui-renderer-snabbdom@latest @servicenow/library-translate@latest

Once that is all done you can do a "npm outdated" again to make sure you have the latest versions.

As far as I have seen ServiceNow does not at the moment at least from what I have seen notify that there is a new version of the Framework so you should probably make a point to check the versions of the packages every now and then.  If someone has seen otherwise please post below.

As always comments/suggestions are always welcome.

Version history
Last update:
‎09-21-2020 09:22 AM
Updated by: