HTML Development
Node.js Versions
3min
as of brightsignos 8 2, two versions of node are shipped with the player a node js version that is integrated into chromium the standalone node js that is used by ronodejs docid\ x9c4jhn6rnqgryfly1wdq and similar objects the version numbers of these are not identical although brightsign tries to ensure that they are at least the same major version note that the embedded node js is associated with rohtmlwidget docid\ xljq5 yhdma2ssmpzimtk and standalone node js is associated with ronodejs docid\ x9c4jhn6rnqgryfly1wdq determining version numbers inspecting process version in each environment is the most reliable way to determine the exact version number for any given version of the os for standalone node js, enter process version at the prompt brightsign> node \> process version 'v10 15 3' \> brightsign> for embedded node js, run a script to print the version number to the log and inspect the output (there is no way to type directly in the console) brightsign> htmlplay data\ text/html,\<script>console log(process version);\</script> brightsign> log \[ ] <12>\[173535 688] \[info] \[source data\ text/html,%3cscript%3econsole log(process version);%3c/script%3e 1] v10 11 0 brightsign> os/chromium version compatibility brightsignos version chromium version embedded node js version standalone node js version os 7 1 x, 7 0 x chromium 45 5 1 1 5 1 1 os 8 0 x chromium 65 10 0 0 8 9 4 os 8 1 x, 8 2 x, 8 3 x chromium 69 10 11 0 10 15 3 os 8 5 x, os 9 0 x chromium 87 14 17 6 14 17 6