I am trying to install NodeJS for windows 7. I tried installing the most recent NodeJS but it is not compatible with Windows 7. I was wondering if anyone knows what is the latest version of NodeJS you can install on Windows 7?
Thank you.
Top-Master
6,6515 gold badges33 silver badges59 bronze badges
asked Jun 5, 2020 at 10:01
Franky McCarthyFranky McCarthy
7171 gold badge4 silver badges5 bronze badges
5
Update: Oct 2021, the latest versions working with below "trick"
are:
- Node v14.16.1 (or older but not below v14.5.0)
- Node v15.8.0 (or older but not below v15.0.0)
Because Node updated from
libuv v1.40
tov1.41
,
and with that, causing Win7 errors:
ws2_32.dll
does not haveGetHostNameW
function (or something alike).
The workaround Method (for versions mentioned above)
The v12.x branch seems to continue supporting Win7 (tested 2021 with Node v12.22.7).
But I needed 14.x version-branch and ended solving problem;
I just installed Node 14.15.0, like:
- Go to Node-downloads
- Download the Windows Binary (.zip) (either 32/64 bit)
- Extract it in the directory where your node is installed and say yes to replace all files (remember that the zip comes with
npm
, which is innode_modules/npm
directory; I didn’t copy from the zip because I already updated npm before replacing the files) - Create an Environment variable called:
NODE_SKIP_PLATFORM_CHECK
and set it to1
- Ready to use Node in Windows 7 for now.
Top-Master
6,6515 gold badges33 silver badges59 bronze badges
answered Oct 31, 2020 at 20:21
17
It seems that v13.14.0 is the last installer that works on Window 7
go here and select the package related to your version of windows 32 / 64 bits:
https://nodejs.org/dist/latest-v13.x/
answered Feb 16, 2021 at 10:18
Node.js is an open-source, cross-platform, JavaScript runtime environment. It
executes JavaScript code outside of a browser. For more information on using
Node.js, see the Node.js Website.
The Node.js project uses an open governance model. The
OpenJS Foundation provides support for the project.
This project is bound by a Code of Conduct.
Table of contents
- Support
- Release types
- Download
- Current and LTS releases
- Nightly releases
- API documentation
- Verifying binaries
- Download
- Building Node.js
- Security
- Contributing to Node.js
- Current project team members
- TSC (Technical Steering Committee)
- Collaborators
- Triagers
- Release keys
- License
Support
Looking for help? Check out the
instructions for getting support.
Release types
- Current: Under active development. Code for the Current release is in the
branch for its major version number (for example,
v15.x). Node.js releases a new
major version every 6 months, allowing for breaking changes. This happens in
April and October every year. Releases appearing each October have a support
life of 8 months. Releases appearing each April convert to LTS (see below)
each October. - LTS: Releases that receive Long Term Support, with a focus on stability
and security. Every even-numbered major version will become an LTS release.
LTS releases receive 12 months of Active LTS support and a further 18 months
of Maintenance. LTS release lines have alphabetically-ordered code names,
beginning with v4 Argon. There are no breaking changes or feature additions,
except in some special circumstances. - Nightly: Code from the Current branch built every 24-hours when there are
changes. Use with caution.
Current and LTS releases follow Semantic Versioning. A
member of the Release Team signs each Current and LTS release.
For more information, see the
Release README.
Download
Binaries, installers, and source tarballs are available at
https://nodejs.org/en/download/.
Current and LTS releases
https://nodejs.org/download/release/
The latest directory is an
alias for the latest Current release. The latest-codename directory is an
alias for the latest release from an LTS line. For example, the
latest-fermium directory
contains the latest Fermium (Node.js 14) release.
Nightly releases
https://nodejs.org/download/nightly/
Each directory name and filename contains a date (in UTC) and the commit
SHA at the HEAD of the release.
API documentation
Documentation for the latest Current release is at https://nodejs.org/api/.
Version-specific documentation is available in each release directory in the
docs subdirectory. Version-specific documentation is also at
https://nodejs.org/download/docs/.
Verifying binaries
Download directories contain a SHASUMS256.txt
file with SHA checksums for the
files.
To download SHASUMS256.txt
using curl
:
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt
To check that a downloaded file matches the checksum, run
it through sha256sum
with a command such as:
$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
For Current and LTS, the GPG detached signature of SHASUMS256.txt
is in
SHASUMS256.txt.sig
. You can use it with gpg
to verify the integrity of
SHASUMS256.txt
. You will first need to import
the GPG keys of individuals authorized to create releases. To
import the keys:
$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
See the bottom of this README for a full script to import active release keys.
Next, download the SHASUMS256.txt.sig
for the release:
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig
Then use gpg --verify SHASUMS256.txt.sig SHASUMS256.txt
to verify
the file’s signature.
Building Node.js
See BUILDING.md for instructions on how to build Node.js from
source and a list of supported platforms.
Security
For information on reporting security vulnerabilities in Node.js, see
SECURITY.md.
Contributing to Node.js
- Contributing to the project
- Working Groups
- Strategic initiatives
- Technical values and prioritization
Current project team members
For information about the governance of the Node.js project, see
GOVERNANCE.md.
TSC (Technical Steering Committee)
- aduh95 —
Antoine du Hamel <duhamelantoine1995@gmail.com> (he/him) - apapirovski —
Anatoli Papirovski <apapirovski@mac.com> (he/him) - BethGriggs —
Beth Griggs <bgriggs@redhat.com> (she/her) - BridgeAR —
Ruben Bridgewater <ruben@bridgewater.de> (he/him) - ChALkeR —
Сковорода Никита Андреевич <chalkerx@gmail.com> (he/him) - cjihrig —
Colin Ihrig <cjihrig@gmail.com> (he/him) - codebytere —
Shelley Vohr <shelley.vohr@gmail.com> (she/her) - danielleadams —
Danielle Adams <adamzdanielle@gmail.com> (she/her) - fhinkel —
Franziska Hinkelmann <franziska.hinkelmann@gmail.com> (she/her) - gabrielschulhof —
Gabriel Schulhof <gabrielschulhof@gmail.com> - gireeshpunathil —
Gireesh Punathil <gpunathi@in.ibm.com> (he/him) - jasnell —
James M Snell <jasnell@gmail.com> (he/him) - joyeecheung —
Joyee Cheung <joyeec9h3@gmail.com> (she/her) - mcollina —
Matteo Collina <matteo.collina@gmail.com> (he/him) - mhdawson —
Michael Dawson <midawson@redhat.com> (he/him) - mmarchini —
Mary Marchini <oss@mmarchini.me> (she/her) - MylesBorins —
Myles Borins <myles.borins@gmail.com> (he/him) - richardlau —
Richard Lau <rlau@redhat.com> - ronag —
Robert Nagy <ronagy@icloud.com> - targos —
Michaël Zasso <targos@protonmail.com> (he/him) - tniessen —
Tobias Nießen <tniessen@tnie.de> (he/him) - Trott —
Rich Trott <rtrott@gmail.com> (he/him)
Emeriti
TSC emeriti
- addaleax —
Anna Henningsen <anna@addaleax.net> (she/her) - bnoordhuis —
Ben Noordhuis <info@bnoordhuis.nl> - chrisdickinson —
Chris Dickinson <christopher.s.dickinson@gmail.com> - danbev —
Daniel Bevenius <daniel.bevenius@gmail.com> (he/him) - evanlucas —
Evan Lucas <evanlucas@me.com> (he/him) - Fishrock123 —
Jeremiah Senkpiel <fishrock123@rocketmail.com> (he/they) - gibfahn —
Gibson Fahnestock <gibfahn@gmail.com> (he/him) - indutny —
Fedor Indutny <fedor@indutny.com> - isaacs —
Isaac Z. Schlueter <i@izs.me> - joshgav —
Josh Gavant <josh.gavant@outlook.com> - mscdex —
Brian White <mscdex@mscdex.net> - nebrius —
Bryan Hughes <bryan@nebri.us> - ofrobots —
Ali Ijaz Sheikh <ofrobots@google.com> (he/him) - orangemocha —
Alexis Campailla <orangemocha@nodejs.org> - piscisaureus —
Bert Belder <bertbelder@gmail.com> - rvagg —
Rod Vagg <r@va.gg> - sam-github —
Sam Roberts <vieuxtech@gmail.com> - shigeki —
Shigeki Ohtsu <ohtsu@ohtsu.org> (he/him) - thefourtheye —
Sakthipriyan Vairamani <thechargingvolcano@gmail.com> (he/him) - TimothyGu —
Tiancheng «Timothy» Gu <timothygu99@gmail.com> (he/him) - trevnorris —
Trevor Norris <trev.norris@gmail.com>
Collaborators
- addaleax —
Anna Henningsen <anna@addaleax.net> (she/her) - aduh95 —
Antoine du Hamel <duhamelantoine1995@gmail.com> (he/him) - ak239 —
Aleksei Koziatinskii <ak239spb@gmail.com> - antsmartian —
Anto Aravinth <anto.aravinth.cse@gmail.com> (he/him) - apapirovski —
Anatoli Papirovski <apapirovski@mac.com> (he/him) - AshCripps —
Ash Cripps <acripps@redhat.com> - Ayase-252 —
Qingyu Deng <i@ayase-lab.com> - bcoe —
Ben Coe <bencoe@gmail.com> (he/him) - bengl —
Bryan English <bryan@bryanenglish.com> (he/him) - benjamingr —
Benjamin Gruenbaum <benjamingr@gmail.com> - BethGriggs —
Beth Griggs <bgriggs@redhat.com> (she/her) - bmeck —
Bradley Farias <bradley.meck@gmail.com> - boneskull —
Christopher Hiller <boneskull@boneskull.com> (he/him) - BridgeAR —
Ruben Bridgewater <ruben@bridgewater.de> (he/him) - bzoz —
Bartosz Sosnowski <bartosz@janeasystems.com> - cclauss —
Christian Clauss <cclauss@me.com> (he/him) - ChALkeR —
Сковорода Никита Андреевич <chalkerx@gmail.com> (he/him) - cjihrig —
Colin Ihrig <cjihrig@gmail.com> (he/him) - codebytere —
Shelley Vohr <shelley.vohr@gmail.com> (she/her) - danbev —
Daniel Bevenius <daniel.bevenius@gmail.com> (he/him) - danielleadams —
Danielle Adams <adamzdanielle@gmail.com> (she/her) - davisjam —
Jamie Davis <davisjam@vt.edu> (he/him) - DerekNonGeneric —
Derek Lewis <DerekNonGeneric@inf.is> (he/him) - devnexen —
David Carlier <devnexen@gmail.com> - devsnek —
Gus Caplan <me@gus.host> (they/them) - dmabupt —
Xu Meng <dmabupt@gmail.com> (he/him) - dnlup
Daniele Belardi <dwon.dnl@gmail.com> (he/him) - edsadr —
Adrian Estrada <edsadr@gmail.com> (he/him) - eugeneo —
Eugene Ostroukhov <eostroukhov@google.com> - evanlucas —
Evan Lucas <evanlucas@me.com> (he/him) - fhinkel —
Franziska Hinkelmann <franziska.hinkelmann@gmail.com> (she/her) - Flarna —
Gerhard Stöbich <deb2001-github@yahoo.de> (he/they) - gabrielschulhof —
Gabriel Schulhof <gabrielschulhof@gmail.com> - gengjiawen —
Jiawen Geng <technicalcute@gmail.com> - GeoffreyBooth —
Geoffrey Booth <webadmin@geoffreybooth.com> (he/him) - gireeshpunathil —
Gireesh Punathil <gpunathi@in.ibm.com> (he/him) - guybedford —
Guy Bedford <guybedford@gmail.com> (he/him) - HarshithaKP —
Harshitha K P <harshitha014@gmail.com> (she/her) - hashseed —
Yang Guo <yangguo@chromium.org> (he/him) - himself65 —
Zeyu Yang <himself65@outlook.com> (he/him) - hiroppy —
Yuta Hiroto <hello@hiroppy.me> (he/him) - iansu —
Ian Sutherland <ian@iansutherland.ca> - indutny —
Fedor Indutny <fedor@indutny.com> - JacksonTian —
Jackson Tian <shyvo1987@gmail.com> - jasnell —
James M Snell <jasnell@gmail.com> (he/him) - jkrems —
Jan Krems <jan.krems@gmail.com> (he/him) - joaocgreis —
João Reis <reis@janeasystems.com> - joyeecheung —
Joyee Cheung <joyeec9h3@gmail.com> (she/her) - juanarbol —
Juan José Arboleda <soyjuanarbol@gmail.com> (he/him) - JungMinu —
Minwoo Jung <nodecorelab@gmail.com> (he/him) - legendecas —
Chengzhong Wu <legendecas@gmail.com> (he/him) - Leko —
Shingo Inoue <leko.noor@gmail.com> (he/him) - linkgoron —
Nitzan Uziely <linkgoron@gmail.com> - lpinca —
Luigi Pinca <luigipinca@gmail.com> (he/him) - lundibundi —
Denys Otrishko <shishugi@gmail.com> (he/him) - Lxxyx —
Zijian Liu <lxxyxzj@gmail.com> (he/him) - mafintosh —
Mathias Buus <mathiasbuus@gmail.com> (he/him) - mcollina —
Matteo Collina <matteo.collina@gmail.com> (he/him) - mhdawson —
Michael Dawson <midawson@redhat.com> (he/him) - miladfarca —
Milad Fa <mfarazma@redhat.com> (he/him) - mildsunrise —
Alba Mendez <me@alba.sh> (she/her) - mmarchini —
Mary Marchini <oss@mmarchini.me> (she/her) - mscdex —
Brian White <mscdex@mscdex.net> - MylesBorins —
Myles Borins <myles.borins@gmail.com> (he/him) - oyyd —
Ouyang Yadong <oyydoibh@gmail.com> (he/him) - panva —
Filip Skokan <panva.ip@gmail.com> - PoojaDurgad —
Pooja D P <Pooja.D.P@ibm.com> (she/her) - puzpuzpuz —
Andrey Pechkurov <apechkurov@gmail.com> (he/him) - Qard —
Stephen Belanger <admin@stephenbelanger.com> (he/him) - RaisinTen —
Darshan Sen <raisinten@gmail.com> (he/him) - rexagod —
Pranshu Srivastava <rexagod@gmail.com> (he/him) - richardlau —
Richard Lau <rlau@redhat.com> - rickyes —
Ricky Zhou <0x19951125@gmail.com> (he/him) - ronag —
Robert Nagy <ronagy@icloud.com> - ruyadorno —
Ruy Adorno <ruyadorno@github.com> (he/him) - rvagg —
Rod Vagg <rod@vagg.org> - ryzokuken —
Ujjwal Sharma <ryzokuken@disroot.org> (he/him) - santigimeno —
Santiago Gimeno <santiago.gimeno@gmail.com> - seishun —
Nikolai Vavilov <vvnicholas@gmail.com> - shisama —
Masashi Hirano <shisama07@gmail.com> (he/him) - silverwind —
Roman Reiss <me@silverwind.io> - srl295 —
Steven R Loomis <srloomis@us.ibm.com> - starkwang —
Weijia Wang <starkwang@126.com> - sxa —
Stewart X Addison <sxa@redhat.com> (he/him) - targos —
Michaël Zasso <targos@protonmail.com> (he/him) - TimothyGu —
Tiancheng «Timothy» Gu <timothygu99@gmail.com> (he/him) - tniessen —
Tobias Nießen <tniessen@tnie.de> (he/him) - trivikr —
Trivikram Kamat <trivikr.dev@gmail.com> - Trott —
Rich Trott <rtrott@gmail.com> (he/him) - vdeturckheim —
Vladimir de Turckheim <vlad2t@hotmail.com> (he/him) - VoltrexMaster —
Voltrex <mohammadkeyvanzade94@gmail.com> (he/him) - watilde —
Daijiro Wachi <daijiro.wachi@gmail.com> (he/him) - watson —
Thomas Watson <w@tson.dk> - XadillaX —
Khaidi Chu <i@2333.moe> (he/him) - yashLadha —
Yash Ladha <yash@yashladha.in> (he/him) - yosuke-furukawa —
Yosuke Furukawa <yosuke.furukawa@gmail.com> - ZYSzys —
Yongsheng Zhang <zyszys98@gmail.com> (he/him)
Emeriti
Collaborator emeriti
- andrasq —
Andras <andras@kinvey.com> - AnnaMag —
Anna M. Kedzierska <anna.m.kedzierska@gmail.com> - AndreasMadsen —
Andreas Madsen <amwebdk@gmail.com> (he/him) - aqrln —
Alexey Orlenko <eaglexrlnk@gmail.com> (he/him) - bmeurer —
Benedikt Meurer <benedikt.meurer@gmail.com> - bnoordhuis —
Ben Noordhuis <info@bnoordhuis.nl> - brendanashworth —
Brendan Ashworth <brendan.ashworth@me.com> - calvinmetcalf —
Calvin Metcalf <calvin.metcalf@gmail.com> - chrisdickinson —
Chris Dickinson <christopher.s.dickinson@gmail.com> - claudiorodriguez —
Claudio Rodriguez <cjrodr@yahoo.com> - DavidCai1993 —
David Cai <davidcai1993@yahoo.com> (he/him) - digitalinfinity —
Hitesh Kanwathirtha <digitalinfinity@gmail.com> (he/him) - eljefedelrodeodeljefe —
Robert Jefe Lindstaedt <robert.lindstaedt@gmail.com> - estliberitas —
Alexander Makarenko <estliberitas@gmail.com> - firedfox —
Daniel Wang <wangyang0123@gmail.com> - Fishrock123 —
Jeremiah Senkpiel <fishrock123@rocketmail.com> (he/they) - gdams —
George Adams <gadams@microsoft.com> (he/him) - geek —
Wyatt Preul <wpreul@gmail.com> - gibfahn —
Gibson Fahnestock <gibfahn@gmail.com> (he/him) - glentiki —
Glen Keane <glenkeane.94@gmail.com> (he/him) - iarna —
Rebecca Turner <me@re-becca.org> - imran-iq —
Imran Iqbal <imran@imraniqbal.org> - imyller —
Ilkka Myller <ilkka.myller@nodefield.com> - isaacs —
Isaac Z. Schlueter <i@izs.me> - italoacasas —
Italo A. Casas <me@italoacasas.com> (he/him) - jasongin —
Jason Ginchereau <jasongin@microsoft.com> - jbergstroem —
Johan Bergström <bugs@bergstroem.nu> - jdalton —
John-David Dalton <john.david.dalton@gmail.com> - jhamhader —
Yuval Brik <yuval@brik.org.il> - joshgav —
Josh Gavant <josh.gavant@outlook.com> - julianduque —
Julian Duque <julianduquej@gmail.com> (he/him) - kfarnung —
Kyle Farnung <kfarnung@microsoft.com> (he/him) - kunalspathak —
Kunal Pathak <kunal.pathak@microsoft.com> - lance —
Lance Ball <lball@redhat.com> (he/him) - lucamaraschi —
Luca Maraschi <luca.maraschi@gmail.com> (he/him) - lxe —
Aleksey Smolenchuk <lxe@lxe.co> - maclover7 —
Jon Moss <me@jonathanmoss.me> (he/him) - matthewloring —
Matthew Loring <mattloring@google.com> - micnic —
Nicu Micleușanu <micnic90@gmail.com> (he/him) - mikeal —
Mikeal Rogers <mikeal.rogers@gmail.com> - misterdjules —
Julien Gilli <jgilli@netflix.com> - monsanto —
Christopher Monsanto <chris@monsan.to> - MoonBall —
Chen Gang <gangc.cxy@foxmail.com> - not-an-aardvark —
Teddy Katz <teddy.katz@gmail.com> (he/him) - ofrobots —
Ali Ijaz Sheikh <ofrobots@google.com> (he/him) - Olegas —
Oleg Elifantiev <oleg@elifantiev.ru> - orangemocha —
Alexis Campailla <orangemocha@nodejs.org> - othiym23 —
Forrest L Norvell <ogd@aoaioxxysz.net> (they/them/themself) - petkaantonov —
Petka Antonov <petka_antonov@hotmail.com> - phillipj —
Phillip Johnsen <johphi@gmail.com> - piscisaureus —
Bert Belder <bertbelder@gmail.com> - pmq20 —
Minqi Pan <pmq2001@gmail.com> - princejwesley —
Prince John Wesley <princejohnwesley@gmail.com> - psmarshall —
Peter Marshall <petermarshall@chromium.org> (he/him) - refack —
Refael Ackermann (רפאל פלחי) <refack@gmail.com> (he/him/הוא/אתה) - rlidwka —
Alex Kocharin <alex@kocharin.ru> - rmg —
Ryan Graham <r.m.graham@gmail.com> - robertkowalski —
Robert Kowalski <rok@kowalski.gd> - romankl —
Roman Klauke <romaaan.git@gmail.com> - ronkorving —
Ron Korving <ron@ronkorving.nl> - RReverser —
Ingvar Stepanyan <me@rreverser.com> - rubys —
Sam Ruby <rubys@intertwingly.net> - saghul —
Saúl Ibarra Corretgé <s@saghul.net> - sam-github —
Sam Roberts <vieuxtech@gmail.com> - sebdeckers —
Sebastiaan Deckers <sebdeckers83@gmail.com> - shigeki —
Shigeki Ohtsu <ohtsu@ohtsu.org> (he/him) - stefanmb —
Stefan Budeanu <stefan@budeanu.com> - tellnes —
Christian Tellnes <christian@tellnes.no> - thefourtheye —
Sakthipriyan Vairamani <thechargingvolcano@gmail.com> (he/him) - thlorenz —
Thorsten Lorenz <thlorenz@gmx.de> - trevnorris —
Trevor Norris <trev.norris@gmail.com> - tunniclm —
Mike Tunnicliffe <m.j.tunnicliffe@gmail.com> - vkurchatkin —
Vladimir Kurchatkin <vladimir.kurchatkin@gmail.com> - vsemozhetbyt —
Vse Mozhet Byt <vsemozhetbyt@gmail.com> (he/him) - whitlockjc —
Jeremy Whitlock <jwhitlock@apache.org> - yhwang —
Yihong Wang <yh.wang@ibm.com> - yorkie —
Yorkie Liu <yorkiefixer@gmail.com>
Collaborators follow the Collaborator Guide in
maintaining the Node.js project.
Triagers
- Ayase-252 —
Qingyu Deng <i@ayase-lab.com> - himadriganguly —
Himadri Ganguly <himadri.tech@gmail.com> (he/him) - iam-frankqiu —
Frank Qiu <iam.frankqiu@gmail.com> (he/him) - marsonya —
Akhil Marsonya <akhil.marsonya27@gmail.com> (he/him) - Mesteery —
Mestery <mestery@pm.me> - PoojaDurgad —
Pooja Durgad <Pooja.D.P@ibm.com> - RaisinTen —
Darshan Sen <raisinten@gmail.com> - VoltrexMaster —
Voltrex <mohammadkeyvanzade94@gmail.com> (he/him)
Release keys
Primary GPG keys for Node.js Releasers (some Releasers sign with subkeys):
- Beth Griggs <bgriggs@redhat.com>
4ED778F539E3634C779C87C6D7062848A1AB005C
- Colin Ihrig <cjihrig@gmail.com>
94AE36675C464D64BAFA68DD7434390BDBE9B9C5
- Danielle Adams <adamzdanielle@gmail.com>
74F12602B6F1C4E913FAA37AD3A89613643B6201
- James M Snell <jasnell@keybase.io>
71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
- Michaël Zasso <targos@protonmail.com>
8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600
- Myles Borins <myles.borins@gmail.com>
C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
- Richard Lau <rlau@redhat.com>
C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C
- Rod Vagg <rod@vagg.org>
DD8F2338BAE7501E3DD5AC78C273792F7D83545D
- Ruben Bridgewater <ruben@bridgewater.de>
A48C2BEE680E841632CD4E44F07496B3EB3C1762
- Ruy Adorno <ruyadorno@hotmail.com>
108F52B48DB57BB0CC439B2997B01419BD92F80A
- Shelley Vohr <shelley.vohr@gmail.com>
B9E2F5981AA6E0CD28160D9FF13993A75599653C
To import the full set of trusted release keys (including subkeys possibly used
to sign releases):
gpg --keyserver pool.sks-keyservers.net --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5 gpg --keyserver pool.sks-keyservers.net --recv-keys 74F12602B6F1C4E913FAA37AD3A89613643B6201 gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1 gpg --keyserver pool.sks-keyservers.net --recv-keys 8FCCA13FEF1D0C2E91008E09770F7A9A5AE15600 gpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8 gpg --keyserver pool.sks-keyservers.net --recv-keys C82FA3AE1CBEDC6BE46B9360C43CEC45C17AB93C gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D gpg --keyserver pool.sks-keyservers.net --recv-keys A48C2BEE680E841632CD4E44F07496B3EB3C1762 gpg --keyserver pool.sks-keyservers.net --recv-keys 108F52B48DB57BB0CC439B2997B01419BD92F80A gpg --keyserver pool.sks-keyservers.net --recv-keys B9E2F5981AA6E0CD28160D9FF13993A75599653C
See the section above on Verifying Binaries for how to
use these keys to verify a downloaded file.
Other keys used to sign some previous releases
- Chris Dickinson <christopher.s.dickinson@gmail.com>
9554F04D7259F04124DE6B476D5A82AC7E37093B
- Danielle Adams <adamzdanielle@gmail.com>
1C050899334244A8AF75E53792EF661D867B9DFA
- Evan Lucas <evanlucas@me.com>
B9AE9905FFD7803F25714661B63B535A4C206CA9
- Gibson Fahnestock <gibfahn@gmail.com>
77984A986EBC2AA786BC0F66B01FBB92821C587A
- Isaac Z. Schlueter <i@izs.me>
93C7E9E91B49E432C2F75674B0A78B0A6C481CF6
- Italo A. Casas <me@italoacasas.com>
56730D5401028683275BD23C23EFEFE93C4CFFFE
- Jeremiah Senkpiel <fishrock@keybase.io>
FD3A5288F042B6850C66B31F09FE44734EB7990E
- Julien Gilli <jgilli@fastmail.fm>
114F43EE0176B71C7BC219DD50A3051F888C628D
- Timothy J Fontaine <tjfontaine@gmail.com>
7937DFD2AB06298B2293C3187D33FF9D0246406D
License
Node.js is available under the
MIT license. Node.js also includes
external libraries that are available under a variety of licenses. See
LICENSE for the full
license text.
26.01.2021
6 комментариев
43 923
Привет! Рассмотрим установку Node.js на Windows 7 и протестируем его работу.
При попытке установить последнюю версию Node.js на Windows 7, в моем случае v14.15.4 LTS (ссылка), возникает ошибка о том, что приложение поддерживается на Windows 8.1. и выше:
1. Находим более раннюю версию, которая подойдёт для Windows 7, перейдем по ссылке (на сайт nodejs.org).
2. Скачиваем версию для вашей операционной системы (у меня ссылка на v13.14.0-x64.msi). Открываем этот файл для установки:
3. В открывшемся окошке подтверждаем свою готовность к установке нажатием кнопки Next:
4. Соглашаемся с условиями лицензионного соглашения, ставим галочку и нажимаем Next:
5. По умолчанию, установка Node.js происходит в папку C: Program Filesnodejs на Вашем компьютере. Поменяйте, при необходимости, и нажимайте Next:
6. Далее идут пользовательские настройки. Предлагается установить дополнительные инструменты — на Ваше усмотрение. Оставляем как есть и нажимаем Next:
7. Видим сообщение об успешной установке, нажимаем Finish:
Мои поздравления 🙂 Node.js установлен.
1. Через Пуск открываем стандартную программу Windows Выполнить , если не нашли Командную строку:
1.1. Командой cmd открываем консоль:
2. Теперь пишем в консоли node -v — так проверяем работу Node.js. Видим на экране установленную версию, в моём случае v13.14.0:
3. Дальше командой npm -v проверяем наличие npm. Видим версию, в моем случае 6.14.4
Всё отлично, мы решили проблему: установили Node.js на Windows 7 и проверили его работу.
Голосов: 94, Средняя оценка: 4.7
Дата: 22.09.2021
Многие пользователи компьютеров до сих пор не перешли на актуальную версию ОС и сидят на Windows 7. Данная версия считается одной из самых популярных и еще долго будет использоваться даже без официальной поддержки.
К сожалению многие разработчики стороннего софта уже сейчас начинают отказываться от поддержки Windows 7. В их числе и разработчики Node.js — популярной среда выполнения JavaScript. Благодаря Node.js разработчики могу запускать свои JS-приложения прямо на компьютере в обход браузера.
Ошибка Node.js на Win 7
Если вы сейчас перейдете на официальный сайт Node.j и скачаете установочный файл для Windows, то при запуске получите ошибку
“The Application is only supported on windows 8.1, windows server 2012 R2, or Higher”
Чтобы установить программу необходимо скачать более раннюю версию Node.js 13.14.0 по ссылке.
После того как скачаете и установите программу проверьте, что Node.js работает. Наберите в командной строке две команды.
Вот так просто можно скачать и установить Node.js на ОС Windows 7, но лучше всего перейти на актуальную версию операционной системы.
nodejs
node.js
windows 7
npm
Не забудьте сказать спасибо. Поставьте лайк!
This post walks through a Node.js install on Windows 7 and tests that node and npm work. It installs v13.14.0 LTS.
It seems that v13.14.0 LTS is the last installer that works on Window 7. I get this error when I try to install v14.0.0 (node-v14.0.0-x64.msi from [link]):
This post also includes a link to the License Agreement so people can review it before installing. The install takes about 30 secs and uses 86 MB.
Steps
1. Go to [link]
2. Click node-v13.14.0-x64.msi or click [link]
3. Click to launch the install
4. Click Run
5. Click Next
6. Click the I accept the terms in the License Agreement checkbox and click Next
Note: A PDF of the 25 page License Agreement is [here] a Word doc is [here]
7. Click Next
Note: Installs Node.js into C:Program Filesnodejs
8. Click Next on the Custom Setup
Note: I’ve expanded the submodules in the picture
Note 2: Clicking on Disk Usage shows that all the features require 86 MB
9. Click Install
10. You’ll see the screen pause, darken and see this pop up. Click Yes.
11. Click Finish
Congratulations! You’ve installed node and npm.
Test
1. (A) Click the Windows Icon, (B) type cmd and (C) click cmd.exe
2. Type node -v. I see v10.14.2.
3. Type npm -v. I see 6.4.1.
…and it works!
Reference
Node.js logo from [link]
Hello there Readers, welcome to the first episode of YPOS(Your Problems Our Solution). In this series we try to solve your each and every problem related to coding and computers which you face in your day to day life.
Today we are going to tell you the tutorial by which you can install Node.js in your Old Antique Windows 7 system [lol just kidding:)].
You may be getting this error dialog box whenever you are trying to install Node.js on your Windows 7. This is because v13.40.0 LTS is the last installer that works on Windows 7.
Doesn’t matter whether you are using Windows 7 Home, Ultimate or Professional, this method works absolutely fine with each of them.
This method hardly takes 1 Minute to install node.js on your Windows 7 and will work completely fine without showing any of the error messages.
So, without wasting your time let’s jump to the Solution of Installing Node.js on your Windows 7.
How to Install Node.js On Windows 7 [ Step by Step Guide]
- To install the last stable version which works absolutely fine on Windows 7. Click this – Click Me
- Select node-v13. 14.0-x64.msi from the list or simply download Directly from Here.
- Click the launch to install Node.js in your system.
- Click Run
- Click Next
- Then Click on I accept the terms in the License Agreement (bla bla bla. . .) and then Click Next.
- Choose the location where you want to install node.js in your system and then click Next.
- Then Click on Next in custom Setup (you don’t have to do anything on this page)
- Finally the moment we were all waiting for “CLICK ON INSTALL”.
- You will see a dialog box popping up after a few seconds, just select Yes and forget about the rest.
- About so much of hard work(=_=), Finally Node.js is installed in your Window 7.
Go and have some fun.
How To Check Whether Node.js is installed on your Windows 7 or Not
So, you want to check whether Node.js is installed in your system or not. That means you don’t have trust in me, Ok then good bye 🙁 [lol just kidding]
Follow these Steps to check Whether node.js is working or not
- Go to Start, type cmd and click on cmd.exe
- Type node and press Enter.
If you can see something like this on your screen, that means Node.js is installed on your Windows 7 and working perfectly.
If you want to check which npm version is installed simply type npm -v and hit that big juicy ENTER key on your keyboard.
You will get to know the npm version installed in your System.
Conclusion
That’s all for today my happy audience. I hope this tutorial helped you to install Node.js on Your Windows 7.
But by any chance, if this method didn’t work out then time to say goodbye to your Old Operating system just throw it out of your window. (lol just kidding, don’t take it seriously) [@[email protected]].
If this method didn’t work out then contact us in the comment section, we would feel delighted to help you.
I will meet you guys next time with an amazing solution like this one. Till then Like the Post and Subscribe our Channel [ohh. . . Sorry, I forgot this is not Youtube]
Share this Post who is in need of this Solution.
Broz Who Code
CodingBroz
As with any programming language, platform, or tool that doesn’t come bundled with Windows, getting up and running with Node.js takes some initial setup before you can start hacking away. In my experience, though Node.js has a far better installation experience on Windows than virtually any other language, platform, or tool that I’ve tried to use — just run the installer, and you’re good to go.
In this quick tutorial, we’ll take a look at how to get Node.js installed on Windows. Once we’ve completed the entirety of the tutorial, you’ll be ready to take the next step with Node.js.
This guide covers installing Node.js on the following versions of Windows: Windows 7, Windows 8, Windows 8.1, and Windows 10. These are the versions that are consistently tested and supported by the Node.js build process at the time of writing.
Step 0: The Quick Guide (TL;DR) to Get Node.js Installed on Windows
Here’s the abbreviated guide, highlighting the major steps:
- Open the official page for Node.js downloads and download Node.js for Windows by clicking the «Windows Installer» option
- Run the downloaded Node.js
.msi
Installer — including accepting the license, selecting the destination, and authenticating for the install.- This requires Administrator privileges, and you may need to authenticate
- To ensure Node.js has been installed, run
node -v
in your terminal — you should get something likev6.9.5
- Update your version of npm with
npm install npm --global
- This requires Administrator privileges, and you may need to authenticate
- Congratulations — you’ve now got Node.js installed, and are ready to start building!
Step 1: Download the Node.js .msi
Installer
As the first step to installing Node.js on Windows, you’ll need to download the installer. You’ll be able to grab the installer from the official downloads page for Node.js.
You’ll be able to download the Windows Node.js installer by clicking the Windows Installer
option at the top of the page — when you click this, you’ll get an MSI installer download. Make sure to save it somewhere that you’ll be able to find it!
Step 2: Run the Node.js Installer
You’ve got the Windows Installer — great! Now, you need to install it on your PC. The installer is a pretty typical Wizard interface for installing software on Windows — there are a few steps to it, but you can have it done in under a minute. You can get through it by following the guide below:
- Welcome to the Node.js Setup Wizard
- Select
Next
- Select
- End-User License Agreement (EULA)
- Check
I accept the terms in the License Agreement
- Select
Next
- Check
- Destination Folder
- Select
Next
- Select
- Custom Setup
- Select
Next
- Select
- Ready to install Node.js
- Select
Install
- Note: This step requires Administrator privlidges.
- If prompted, authenticate as an Administrator
- Select
- Installing Node.js
- Let the installer run to completion
- Completed the Node.js Setup Wizard
- Click
Finish
- Click
Step 3: Verify that Node.js was Properly installed
To double check that Node.js was installed fully on your PC, you can test the following command in your Command Prompt (regardless of if you’re using cmd.exe
, Powershell
, or any other command prompt):
$ node -v
If Node.js was installed fully, the command prompt will print something similar to (but probably not exactly) this:
$ node -v // The command we ran - prints out the version of Node.js that's currently installed
v6.9.5 // The printed version of Node.js that's currently installed - v6.9.5 was the most current LTS release at the time of writing.
Step 4: Update the Local npm Version
As the final step in getting Node.js installed, we’ll update your version of npm — the package manager that comes bundled with Node.js.
Node.js always ships with a specific version of npm — Node.js doesn’t (and shouldn’t!) automatically update npm. The release cycle of the npm CLI client isn’t in sync with the Node.js releases. Because of this, there’s almost certainly going to be a newer version of npm available than the one that is installed as a default in any given Node release.
To quickly and easily update npm
, you can run the following command:
npm install npm --global // Update the `npm` CLI client
Now you’ve got Node.js on Windows machine. It’s time to start exploring!
Luckily, we’ve got your back. We’ve written a bunch of articles to help you get started with Node.js! If you’re interested in exploring ES6, you should check out our article on some of the most exciting ES6 features in Node.js. If you’re interested in ways to collaborate with your team a bit better, you should check out our tutorial on using ESLint in projects to improve team collaboration through code standards. Maybe you’d just like to start deploying the applications you’re about to build? In that case, take a peek at our guide on how to deploy Node.js apps on Linux with systemd!
That said, if you want to keep in touch with Node.js and the surrounding ecosystem, you should go follow @NodeSource on Twitter! We’ll keep you updated with important news from the Node.js project, and share the best Node.js tutorials, guides, and tools that the community has to offer.