# \[request\] Plexamp headless - Node requirements **URL:** \ **Category:** Plex Labs\ **Tags:** plexamp\ **Created:** [October 5, 2024, 4:54pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443 "2024-10-05T16:54:14Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![vtr1000](https://avatars.discourse-cdn.com/v4/letter/v/76d3ee/32.png) [@vtr1000](https://forums.plex.tv/u/vtr1000)\ **Post date:** [October 5, 2024, 4:54pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/1 "2024-10-05T16:54:14Z")
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](https://plexamp.plex.tv/headless/version.json) for the latestVersion and updateUrl. Could you add the Node requirement to this response too? So a response may look like: `{ "latestVersion": "4.11.2", "updateUrl": "https://plexamp.plex.tv/headless/Plexamp-Linux-headless-v4.11.2.tar.bz2, "node": "20.4.2" }` 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. Keep the music playing! 🙂 ---
**Author:** ![elan](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/elan/32/5_2.png) [@elan](https://forums.plex.tv/u/elan)\ **Post date:** [October 7, 2024, 8:29pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/2 "2024-10-07T20:29:28Z")
That is a clever idea, unfortunately the feed is generated by electron-updater automatically and I don’t _think_ we have the ability to change it. ---
**Author:** ![vtr1000](https://avatars.discourse-cdn.com/v4/letter/v/76d3ee/32.png) [@vtr1000](https://forums.plex.tv/u/vtr1000)\ **Post date:** [October 7, 2024, 9:25pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/3 "2024-10-07T21:25:35Z")
Thanks for the reply Elan. Shame that… Out of interest, is the download metadata published on the website automatically generated too? I.e. in [https://www.plex.tv/media-server-downloads/?cat=headless&plat=raspberry-pi#plex-plexamp](https://www.plex.tv/media-server-downloads/?cat=headless&plat=raspberry-pi#plex-plexamp) you have: `

A spare Raspberry Pi and Node 20
Plex Pass Subscription Required

v.4.11.2

` 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? Thanks again 🙂 ---
**Author:** ![elan](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/elan/32/5_2.png) [@elan](https://forums.plex.tv/u/elan)\ **Post date:** [October 7, 2024, 9:44pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/4 "2024-10-07T21:44:17Z")
It’s manually produced 😅 > [@vtr1000](#): > > I take it that the packaged node\_modules could be at or below the required level 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. ---
**Author:** ![vtr1000](https://avatars.discourse-cdn.com/v4/letter/v/76d3ee/32.png) [@vtr1000](https://forums.plex.tv/u/vtr1000)\ **Post date:** [October 7, 2024, 10:05pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/5 "2024-10-07T22:05:22Z")
Damn, you don’t make things easy 😉 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)? ---
**Author:** ![elan](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/elan/32/5_2.png) [@elan](https://forums.plex.tv/u/elan)\ **Post date:** [October 7, 2024, 10:19pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/6 "2024-10-07T22:19:30Z")
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. ---
**Author:** ![vtr1000](https://avatars.discourse-cdn.com/v4/letter/v/76d3ee/32.png) [@vtr1000](https://forums.plex.tv/u/vtr1000)\ **Post date:** [October 7, 2024, 10:26pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/7 "2024-10-07T22:26:09Z")
That’ll be fun, I’m sure. PlexOS? 👀 ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [January 5, 2025, 10:26pm UTC](https://forums.plex.tv/t/request-plexamp-headless-node-requirements/891443/8 "2025-01-05T22:26:33Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.