You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running npm install with node lts/iron (v20.17.0), the install reports that the drivelist package does not support that node version, like below. I see jetson-flash package.json specifies only node>=16. So, I dropped the node version down to lts/hydrogen (v18.20.4) to remove the warning.
[2024-09-23 -- The statement below from the original post of this issue is wrong. Drivelist up to v11.1.1 supports node >=16 < 19. Drivelist v11.2.0 supports node >=16, and drivelist v12.0.0 supports node >=18 -- so it still supports node 18. So the issue is that my jetson-flash build used drivelist v11.1.0. The problem is more about package resolution from jetson-flash -- at least when I tested. Let me recreate the test.]
The drivelist package dropped support for node v18 in its v12.0.0. Time to update nodelist to latest (v12.0.2) and update jetson-flash node version requirement to >=20 as well?
When running
npm install
with node lts/iron (v20.17.0), the install reports that the drivelist package does not support that node version, like below. I see jetson-flashpackage.json
specifies only node>=16. So, I dropped the node version down to lts/hydrogen (v18.20.4) to remove the warning.[2024-09-23 -- The statement below from the original post of this issue is wrong. Drivelist up to v11.1.1 supports node
>=16 < 19
. Drivelist v11.2.0 supportsnode >=16
, and drivelist v12.0.0 supportsnode >=18
-- so it still supports node 18. So the issue is that my jetson-flash build used drivelist v11.1.0. The problem is more about package resolution from jetson-flash -- at least when I tested. Let me recreate the test.]The drivelist package dropped support for node v18 in its v12.0.0. Time to update nodelist to latest (v12.0.2) and update jetson-flash node version requirement to >=20 as well?
The text was updated successfully, but these errors were encountered: