Go to https://omahaproxy.appspot.com/ Find the latest stable Chrome version in the table. Check the v8_version column (to the right) on the same row.
To see if Node is installed, open the Windows Command Prompt, Powershell or a similar command line tool, and type node -v . This should print the version number so you'll see something like this v0. 10.35 .
js 8.0. 0 ships with npm 5. Let's highlight major changes in npm 5.
V8 is required for the current Node. js engine to function.
One-line solution:node -p process.versions.v8
Alternative solution:node -e "console.log(process.versions.v8)"
Easy way:
Type in command line: node -p process.versions.v8
Hard way:
Type node --version to get the Node.js version.
Go to the Node.js Changelogs.
Find and open an appropriate Node.js version change log.
Look for notes containing V8 to.
Just run npm version (don't know since when this is available)
> npm version
{ http_parser: '1.0',
node: '0.10.35',
v8: '3.14.5.9',
ares: '1.9.0-DEV',
uv: '0.10.30',
zlib: '1.2.8',
modules: '11',
openssl: '1.0.1j',
npm: '1.4.28',
xsjs: '0.1.5' }
To check your version, check the value in process.versions in the REPL.
node -e "console.log(process.versions.v8);"
Additionally, you can compile node with other versions of V8 if you desire. Obviously results may vary widely here depending on what versions you choose.
cd node-v0.x.x
rm -rf deps/v8
git clone http://github.com/v8/v8.git deps/v8
./configure
make
make install
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With