Author Topic: Node.js - LTS not distinct  (Read 1145 times)

Offline mc_edwards

  • Newbie
  • *
  • Posts: 2
    • View Profile
Node.js - LTS not distinct
« on: September 01, 2020, 02:36:33 PM »
I just inadvertently updated a dev's Node.js from 12.8.3 to 14 using the main Node.js x64 update (Intune only).  This seems to be a quirk from the Node.js .msi, as their version 14 .msi and their LTS .msi have the same upgrade code (but different product codes) (see attachment).

Should the Intune update for [Node.js x64] have a requirement script that considers the product code for version 12 not applicable?

Offline Cody Mathis

  • Administrator
  • Jr. Member
  • *****
  • Posts: 84
    • View Profile
Re: Node.js - LTS not distinct
« Reply #1 on: September 01, 2020, 08:31:37 PM »
Hi there, looks like we might need a major version filter on this! I'll do some testing and let you know.

Offline Cody Mathis

  • Administrator
  • Jr. Member
  • *****
  • Posts: 84
    • View Profile
Re: Node.js - LTS not distinct
« Reply #2 on: September 02, 2020, 10:43:22 AM »
Hello,

We have just updated this on our end.

Can you please delete your Intune Application / Update for Node.JS, and then run a sync in the Publisher to recreate the app?

Node.JS NON LTS should now only update a version 14 install. So the Node.JS app will not update the version 10, or version 12 versions of Node.js.

Worth noting, it will also not update a version 13 build.

Let us know if this solves your issue.

Offline mc_edwards

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Node.js - LTS not distinct
« Reply #3 on: September 02, 2020, 03:21:19 PM »
Confirmed:  device with 12.8.3 installed WILL not be upgraded to version 14 now...thanks for fixing so quickly!

Offline Cody Mathis

  • Administrator
  • Jr. Member
  • *****
  • Posts: 84
    • View Profile
Re: Node.js - LTS not distinct
« Reply #4 on: September 02, 2020, 03:23:36 PM »
Good to hear! Thanks for making us aware of the issue.