HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nwjs
nw.js
JavaScript2012–2022
nwjs / nw.js

nw.js

Call all Node.js modules directly from DOM/WebWorker and enable a new way of writing applications with all Web technologies.

82Distinct people
92Mentions
0Explicit recommenders
41.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Call all Node.js modules directly from DOM/WebWorker and enable a new way of writing applications with all Web technologies.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year92 dated mentions

Observed mentions: 2012-05-12 13:46:26 UTC to 2022-06-09 09:54:49 UTC.

01020302012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 28 mentions; 2 submissions, 26 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 33 mentions; 5 submissions, 28 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 13 mentions; 3 submissions, 10 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC817
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC28226
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC33528
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC13310
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC404
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202

What Hacker News says

13 sources
Was recently looking for information on building desktop apps with Electron or NW.js. Found a few useful links regarding source code protection. In short: Documented method is v8 snapshots. They are compiled code, run slower and are not cross platform. * Using v8 snapshots - https://github.com/nwjs/nw.js/wiki/Protect-JavaScript-source... * Electron thread about source code protection - https://github.com/atom/electron/issues/3041 The second link has a lot of comments with useful information. One of them mentions that v8 snapshot format is documented and also that the actual code is shipped with the snapshot for future optimizations. nw.js just removes the sourcecode from the snapshot. I'm curious if there is any reliable means of source code protection for Electron or NW.js apps.
In Building a cross-platform desktop app with NW.js, React and Flux
You simply zip the files and rename to dot nw. Then the first time the user runs the file, the user needs to select "open with nw.exe". ref: https://github.com/nwjs/nw.js/wiki/How-to-package-and-distri... You probably want to include an "install" script that: * Download and install nwjs if it doesn't exist * Make the "package" open with nw.exe * optionally: Create a shortcut to the "package" on the desktop * optionally: Set a icon for the shortcut Or instruct the user on how to do it. Many files work that way, that you have to select a program to open it with, so the user probably already knows how to do it.
In Atom 1.0
"NW.js appears to be some sort of "break" from node-webkit, and the copy on the main site seems to suggest that it is an entirely new project" It's seems that it's the same project. The GitHub page says: "node-webkit is renamed NW.js" https://github.com/nwjs/nw.js
In NW.js
Honestly, I wonder why they don't bother to put an example on the main page. Looking at the github repo of the project [0] (which doesn't have a folder "example" as well), it says: node-webkit is an app runtime based on Chromium and node.js. You can write native apps in HTML and JavaScript with node-webkit. It also lets you call Node.js modules directly from the DOM and enables a new way of writing native applications with all Web technologies. So I suppose it's about desktop apps ("native" must mean "desktop"). [0] https://github.com/nwjs/nw.js
In NW.js

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.