NitroBolt Desktop

NitroBolt as a desktop app. A fork of the TurboWarp Desktop app.

If you're looking for downloads, checkout the releases.

Licensed under the GPLv3.0. See LICENSE for more information.

Website

The website source code is in the docs folder.

Development

We use submodules, so clone using:

git clone --recursive https://github.com/Nitro-Bolt/desktop nitrobolt-desktop

or run this after cloning:

git submodule init
git submodule update

Install dependencies using:

pnpm i

You can also link other components (i.e. scratch-gui):

# this is assuming scratch-gui and desktop are under the same parent folder
pnpm i
pnpm run build

cd ../desktop
pnpm i
pnpm link ../scratch-gui

Important

If you're looking to develop, for example, scratch-paint, you would only link scratch-gui to desktop, and have scratch-paint linked to scratch-gui.

Then fetch extra library, packager, and extension files using:

pnpm run fetch

Repeat the three previous sets of commands every time you pull changes from GitHub.

Due to the security requirements mandated by custom extensions existing, our desktop app is significantly more complicated than Scratch's.

• src-main is what runs in Electron's main process. There is no build step; this code is included as-is. src-main/entrypoint.js is the entry point to the entire app.
• src-renderer-webpack runs in an Electron renderer process to make the editor work. This is built by webpack as dist-renderer-webpack.
• src-renderer also runs in an Electron renderer process, but without webpack. This is used for things like the privacy policy window.
• src-preload runs as preload scripts in an Electron renderer process. They export glue functions to allow renderer and main to talk to each other in a somewhat controlled manner.
• dist-library-files and dist-extensions contain additional static resources managed by npm run fetch

To build the webpack portions in src-renderer-webpack for development builds, run this:

pnpm run webpack:compile

Once compiled and fetched, you can start an Electron instance for development:

pnpm run electron:start

The app icon won't work in the development version, but it will work in the packaged version.

We've found that development can work pretty well if you open two terminals side-by-side and run pnpm run webpack:watch in one and pnpm run electron:start in the other. You can refresh the windows with ctrl+R or cmd+R for renderer file changes to apply, and manually restart the app for main file changes to apply.

Linux sandbox helper error

On some Linux distributions, Electron will crash with the message The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/.../turbowarp-desktop/node_modules/electron/dist/chrome-sandbox is owned by root and has mode 4755.. Notably we have seen this happen on Debian 10 and earlier and Ubuntu 24.04 and later.

For development, run electron_build_fix_until_reboot.sh, or you can run these commands to enable unprivileged user namespaces until you reboot:

# Enable unprivileged user namespaces.
sudo sysctl -w kernel.unprivileged_userns_clone=1

# Stop AppArmor from preventing unprivileged user namespace creation by default.
# If your distribution does not use AppArmor then you can ignore the error.
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

There are ways to make this permanent, but we don't think you should be making permanent kernel configuration changes just to develop this app.

This error won't happen in the final deb package, rpm package, Flathub, or Snap releases. It will in the in the AppImage.

Final production-ready builds

The development version of the app will be larger and slower than the final release builds.

Build an optimized version of the webpack portions with:

pnpm run webpack:prod
# this seems to dramatically reduce package

Then to package up the final Electron binaries, use either our build script release-automation/build.mjs (see release-automation/README.md) or the electron-builder CLI. Either way the final builds are saved in the dist folder. Here are some examples using the electron-builder CLI directly:

# You can also do manual builds with electron-builder's CLI, for example:
# Windows installer
pnpm dlx electron-builder --windows nsis --x64
# macOS DMG
pnpm dlx electron-builder --mac dmg --universal
# Linux Debian
pnpm dlx electron-builder --linux deb

# Or, you can do multiple at once.
# Windows and Linux Installers and Portables
pnpm dlx electron-builder -w nsis portable -l deb rpm appimage

You can usually package cross-platform (i.e. Linux can build for Windows), but it isn't guaranteed possible

Code signing policy (IGNORE)

TurboWarp Desktop uses a free code signing provided by SignPath.io, certificate by SignPath Foundation.

• Approvers:
  • GarboMuffin
• Privacy policy: https://desktop.turbowarp.org/privacy.html

Advanced customizations

NitroBolt Desktop lets you configure custom JS and CSS without rebuilding the app.

Find NitroBolt Desktop's data path by using the list below or by clicking "?" in the top right corner, then "Desktop Settings", then "Open User Data", then opening the highlighted folder, or refer to this list:

• Windows (except Microsoft Store): %APPDATA%/nitrobolt-desktop
• Microsoft Store: Open %LOCALAPPDATA%/Packages, find the folder with the word NitroBoltDesktop in it, then open LocalCache/Roaming/nitrobolt-desktop
• macOS (except Mac App Store): ~/Library/Application Support/nitrobolt-desktop
• Mac App Store: ~/Library/Containers/org.nitrobolt.desktop/Data/Library/Application Support/nitrobolt-desktop (note that the org.nitrobolt.desktop part may appear as NitroBolt in Finder)
• Linux (except Flatpak and Snap): ~/.config/nitrobolt-desktop
• Linux (Flatpak): ~/.var/app/org.nitrobolt.NitroBolt/config/nitrobolt-desktop
• Linux (Snap): ~/snap/nitrobolt-desktop/current/.config/nitrobolt-desktop

Create the file userscript.js in this folder to configure custom JS. Create the file userstyle.css in this folder to configure custom CSS. Completely restart NitroBolt Desktop (including all windows) to apply.

Uninstall

See https://desktop.turbowarp.org/uninstall