I have a minor feature request that could help a lot of people with automating the update of Plexamp & its node dependency. You currently provide an API endpoint for the latestVersion and updateUrl. Could you add the Node requirement to this response too? So a response may look like:
If there’s any reason that you couldn’t do this, could you confirm whether your node requirement reflects that of the included node_modules? In that case, one could at least be confident in processing their package.json files.
<div class="download-meta"><p>A spare Raspberry Pi and Node 20<br> <a target="_blank" href="https://www.plex.tv/plex-pass/">Plex Pass Subscription Required</a></p> <p id="version">v.4.11.2</p> <!----></div>
If that’s automatically produced, then it’ll probably do the job.
I take it that the packaged node_modules could be at or below the required level and therefore likely to cause issues if relied upon for their devDependencies?
I would assume so, yeah. I was thinking you might be able to inspect treble.node for symbols which might indicate the version of the node API used, but I couldn’t quickly find a way to do that.
Oh well. If you do think of something, it’d be greatly appreciated. The only other thing I can think of is adding a file to the download archive which states the deps (like your own package.json or similar)?
It’s definitely something we’d like to address in the future. The multiroom stuff has its own upgrade system, and we’ll need to have that upgrade node if required as well.
