Elgato_dark/void
1
0
Fork 0
mirror of https://github.com/voideditor/void synced 2026-05-23 09:28:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update VOID_CODEBASE_GUIDE.md

Browse source
This commit is contained in:
Andrew Pareles 2025-04-09 21:17:15 -07:00 committed by GitHub
parent 6230971dff
commit 85759eeb4a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
VOID_CODEBASE_GUIDE.md
View file

@ -25,8 +25,8 @@ Here is some important terminology you should know if you're working inside VSCo
Here's a minimal VSCode rundown if you're just getting started with Void:
- VSCode is (and therefore Void is) an Electron app. Electron runs two processes: a **main** process (for internal workings) and a **browser** process (browser means HTML in general, not just "web browser").
- Code in a `browser/` folder lives in the browser, so it can use window and other browser items
- Code in an `electron-main/` lives on the main process, so it can import node_modules.
- Code in a `browser/` folder lives in the browser, so it can use `window` and other browser items.
- Code in an `electron-main/` lives on the main process, so it can import `node_modules`.
- Code in `common/` can be imported by either one.
- The browser environment is not allowed to import `node_modules`, but there are two workarounds:
1. Bundle the node_module code and ship it in the browser - we're doing this for React.