Repository navigation
NODE 0.9.0 (beta)
NODE 0.9.0 is the first beta. Thank you for testing it.
Which file to download
Scroll down to Assets and download one file:
| Your computer | Download |
|---|---|
| Mac with an Apple chip (M1, M2, M3, M4 or later) | NODE-0.9.0-mac-arm64.dmg |
| Mac with an Intel processor | NODE-0.9.0-mac-x64.dmg |
| Windows | NODE-0.9.0-win-x64.exe |
| Linux | NODE-0.9.0-linux-x86_64.AppImage |
Not sure which Mac you have? Click the Apple menu in the top-left corner and choose About This Mac. If the line "Chip" says Apple M1, M2, M3 or M4, download the Apple chip file. If it says "Processor" with Intel, download the Intel file.
You can ignore the other files, including Source code (zip) and Source code (tar.gz). They are for developers.
Installing on a Mac
- Open the downloaded
.dmgfile. - Drag NODE into the Applications folder.
- Open NODE from Applications. macOS shows a message that it cannot check NODE. Click Done.
- Open System Settings → Privacy & Security. Scroll down to the message about NODE and click Open Anyway. Confirm with your password or Touch ID.
This happens because the beta is not signed with Apple yet. You only need to do it once.
Updates on a Mac: until NODE is signed, it cannot update itself. When a new version comes out, download it from this page and drag it into Applications again, replacing the old one.
Installing on Windows
- If your browser warns about the download, choose Keep.
- Open the
.exefile. If you see "Windows protected your PC", click More info, then Run anyway. - Follow the installer.
Windows copies of NODE check for updates and install them by themselves.
Installing on Linux
Download the .AppImage file, make it executable (right-click → Properties → Allow executing, or chmod +x), and open it.
Known limits in this beta
- Signing in to Google accounts opens in a separate Chrome-based window.
- On a Mac, passkeys (Touch ID / iCloud Keychain sign-in) are turned off; sites offer password sign-in instead.
Reporting a problem
In NODE, open Help → Copy diagnostics and paste the result into a new issue at https://github.com/westernCasa/node_browser/issues, with a short description of what happened.