Package: shinyelectron 0.2.1

Why use one | Getting a config file in place | Complete reference | How values get resolved | File paths | Section reference | app | Settle the slug before you ship | build | Cross-platform caveats | icon and icons | Creating icons | window | server | nodejs | auto_install is planned, not yet active | dependencies | Version keys | Detection and extra packages | R-specific dependency options | Pruning the bundled R runtime | Local R packages | Python-specific dependency options | system_packages | container | apps | logging | lifecycle | signing | installer | Decide on per_machine before the first release | Build Windows installers on Windows | Common recipes | Development setup | Production multi-platform build | Native R app with bundled runtime | Multi-app suite | What happens when a value is invalid | Next steps

Install the package | Run a pre-flight check | Build a demo end to end | Try a prebuilt demo | Export your Shiny app | Shinylive: runs in the browser | Native: runs a real R or Python process | Choose an app type and runtime strategy | What export produces | Build for several platforms in one call | Give the app a custom icon | Capture build settings in a config file | Where to go next | Function cheat sheet

Picking a strategy | Shinylive strategy | The export flow | Tradeoffs | System strategy | The launch flow | Bundled strategy | The build flow | Local R packages | Auto-download strategy | Container strategy | Platform considerations | Portable runtime coverage | Cross-platform builds | macOS code signing | Next steps

When signing matters | Turning signing on | macOS: sign and notarize | Windows: sign with a code signing certificate | Linux: optional GPG signing | Signing in CI | Development versus production | Environment variables reference | Next steps

Start with a full report | Targeted diagnostics | Local versus system Node.js | Reading sitrep results in code | Install-time problems | Node.js not found | Node.js version too old | npm not found | Missing R packages | Xcode Command Line Tools missing (macOS) | Visual Studio Build Tools missing (Windows) | Build tools missing (Linux) | Python not found | Python shinylive CLI not working | Python shiny package not installed | Docker or Podman not found | Docker on Parallels and other nested virtualization | Build-time problems | package.json not found | node_modules not found | Container image pull failure | Container port conflict | GNU tar versus bsdtar on Windows | EBUSY file locks when rebuilding (Windows) | Slow builds (Windows) | Runtime problems | R not on PATH (Windows) | Gatekeeper blocks the app (macOS) | SmartScreen blocks the installer (Windows) | Clear the cache | Debugging a packaged app | Deprecation warnings: shinylive as an app type | Getting help | Next steps

Lifecycle window | Splash | Preloader | Advanced lifecycle options | System tray | What the buttons do | Tray menu | Tray icon, per platform | Application menu | What each template ships | Platform conventions | About dialog | DevTools | Wiring it all together | Editing config from R | Next steps

Layout | R suite | Python suite | Configuration | R suite config | Python suite config | Fields in an apps entry | Mixed-strategy suites | How dependencies are handled | R apps | Python apps | Exporting a suite | Launcher and app switching | One runtime, one active app | Building your own suite

Pick a publish host | Quick start | GitHub Releases | Configure the app | Build the app | Publish a release | What the user sees | Configuration | Three knobs, one pipeline | Private repositories | S3 | Generic HTTP | Code signing | macOS | Windows | Turning updates off | Troubleshooting | The check fails | Downloads, never installs | Always "No updates available" | Debug logging | Publishing from CI | Next steps

Why automate | Before you start | Use the bundled workflow | Configure it | What the matrix builds | Push and tag | Status badge | Customising | App in a different folder | Narrower platform list | Runtime strategy | Icons and other options | Config file wins, action inputs override | Signing in CI | Roll your own | CI-specific troubleshooting | appdir points at the wrong directory | Linux build fails on missing libraries | shinylive build stops with "there is no package called ..." | Pin the shinyelectron version | Job hits the six-hour limit | Next steps

When to reach for a container | Prerequisites | The launch flow | Configuration | Where the image comes from | Built-in R image | Built-in Python image | System dependency baking | Registry image | Passing volumes and env vars | Verifying the engine | Limitations | Platform notes

Why a local install | Installing | Which Node.js shinyelectron uses | Auto-install from _shinyelectron.yml (planned) | Not yet implemented | Cache layout | Download integrity | Clearing the cache | Local versus system | Troubleshooting | Network error during download | Checksum mismatch | Wrong architecture | Local install skipped | Next steps

Two processes, one trust boundary | What shinyelectron locks down | Content-Security-Policy scope | Cross-origin headers (Shinylive only) | Runtime download integrity | Where your app still has to think | Inputs are user-controlled | File access is user-wide | Secrets and per-user credentials | Giving each user their own token | Never bundle credentials | Strategy-specific notes | Shinylive | System, bundled, auto-download | Container | Distribution | What not to do | Do not modify these settings in the generated Electron code | Summary