Use npm list to get the version of elastic-apm-node

[reakaleek]

No description provided.

[trentm]

Why this change? What problem was being solved here?

[v1v]

vnull

$ jq -r '.dependencies."elastic-apm-node".version' package-lock.json
null

[trentm]

Okay, thanks.

It looks like this commit changed the package-lock.json lockfileVersion:

commit 03a52ab96be71449e22243ce3a491cb45c967b10
Author: apmmachine <58790750+apmmachine@users.noreply.github.com>
Date:   2023-11-27T14:55:13-08:00 (5 months ago)

    Bump elastic-apm-node to latest version (#210)


diff --git a/package-lock.json b/package-lock.json
index 41f60b9..ba203d0 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,46 +1,85 @@
 {
   "name": "opbeans-node",
   "version": "1.0.0",
-  "lockfileVersion": 1,
+  "lockfileVersion": 3,
   "requires": true,

A possible alternative to doing the npm ci would be to use npm ls with the --package-lock-only option. From npm help ls:

   package-lock-only

       •   Default: false

       •   Type: Boolean

       If set to true, the current operation will only use the package-lock.json, ignoring node_modules.

       For update this means only the package-lock.json will be updated, instead of checking node_modules and downloading dependencies.

       For list this means the output will be based on the tree described by the package-lock.json, rather than the contents of
       node_modules.

This is a subtle usage that I only happened upon earlier this year.

% npm ls --package-lock-only elastic-apm-node --json
{
  "version": "1.0.0",
  "name": "opbeans-node",
  "dependencies": {
    "elastic-apm-node": {
      "version": "4.5.2",
      "resolved": "https://registry.npmjs.org/elastic-apm-node/-/elastic-apm-node-4.5.2.tgz",
      "overridden": false
    }
  }
}

% npm ls --package-lock-only elastic-apm-node --json  | jq -r '.dependencies."elastic-apm-node".version'
4.5.2

The npm ci step is >90% of the time spent on the "create-tag" workflow, so that would be a nice win.