Gate the build on checkup() | Annotate the diff with ci_report() | Add a GitHub Actions job | Fail loudly | Tune the examination | Keep the report | Expect skipped checks | Check before you commit | See also

Close the gap | Install checktor | Run a first checkup | Read the results as data | Gate a script on one call | Treat what it finds | Examine one category at a time | Check only what CRAN receives | Turn down the volume | Ask for a check, or turn one off | Fit it into your workflow | See also

Read the four outcomes | Build and install | Read the metadata | Check the R code | Check the documentation | Run the examples, tests and vignettes | Add the CRAN incoming checks | Clean up | Expect a few extra steps | Pick up where it stops

Read the severity | Which checks run | Code checks | DESCRIPTION checks | Documentation checks | Example, vignette and demo checks | General checks | CRAN policy checks | Leave two recipes to people | Resolve a disagreement

Shape a check | Use the helpers | read_r_xml(path) | xpath_lints(parsed, xpath, label = NULL) | undesirable_function_check(parsed, funs, label = TRUE) | not_under_fn_with_call_xpath(funs) | extract_rd_section(rd, tag) and collect_rd_text(node, skip) | Build a check for Sys.setenv() | Navigate the parse tree | Try a query | Register the check | Configure an existing check | Trust the parse tree | See also

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

Look before you leap | Extracting the files | The round trip is lossless | Shinylive links decode too | Many links at once | Reading links livelink did not create | Getting just the URL

The idea | Your first link | Comments and expression input | Making it run on arrival | Choosing what they see | A Shiny app instead | Why a string, and not a braced expression? | What a link actually looks like | Going the other way | Links inside a document | Where to next

The hook: output and a link | The engine: a link, and no execution | There is no {shinylive-r} chunk | Chunk options | echo does not do what you might think | Setting options once | Why not a braced expression? | Every chunk option

The same picture, twice | So which do you reach for? | The ggplot is a shell | The short version

What paintr draws | Two backends: paint_ and gpaint_ | Vectors | Matrices | Data frames | Lists | Arrays | Picking a legible device size | Where next

A highlight is a logical mask | The three builders | A comparison is already a mask | A different colour | Highlighting works on every structure | Base and ggplot2, the same mask

webR projects | Describing the files | Write the list inside the call | Running something on arrival | Where the files land | Shiny apps | Why that chunk is not run | Editor or app? | mode is not panels | Python | A directory at a time | How big can a link get?

Exercise and solution pairs | Choosing what students see | A whole folder of scripts | One link per file, or one link for the folder? | Embedding links in your notes | Collecting work back in

Overview | The Traditional Shiny Model | The Shinylive Transformation: From Server to Browser | Step 1: Code Preparation | Dependency Management | File System Considerations | External Resource Management | Step 2: The Conversion Process | Initiating the Conversion | Behind the Scenes | File Collection | Metadata and Manifest Generation | Runtime Environment Setup | Step 3: Browser Deployment and Execution | Local Deployment | Global Deployment | Global Deployment Tutorials | Application Runtime Flow | Understanding and Extracting Shinylive Applications with peeky | Application Reconstruction | Handling Quarto-Embedded Applications | Security Implications | Best Practices for Deployment | Design for Transparency | Data and Algorithm Protection | Clear Licensing and Attribution | Hybrid Deployment Strategy | Fin | Acknowledgements | References

Overview | DESCRIPTION file | Makevars inside the src/ Directory

Frequently Asked Questions | General Questions | What is the searcher package? | How do I install the package? | Why would I use searcher instead of manually searching in a browser? | Which platforms does searcher support? | Search Functionality | How do I search for a specific term? | How do I ensure my search results are R-specific? | Which search engine is best for R-related questions? | Working with Errors | How do I search for an error message? | Can I automatically search errors when they occur? | Is there a way to search warnings too? | AI Assistant Integration | How do I use AI assistants with searcher? | Do I need API keys to use the AI features? | How do I customize how AI assistants respond to my queries? | Prompt Management | What is the prompt management system? | How do I use the built-in prompts? | Can I create my own prompts? | Customization | How do I customize the default behavior of searcher? | How do I change the default search keyword from "base" to "tidyverse"? | How can I reduce or increase the delay before the browser opens? | Comparing AI Solutions | How does searcher's AI assistant integration differ from the ellmer package? | Interface Differences | Use Case Differences | Complementary Usage | Troubleshooting | My browser doesn't open when I use a search function. What's wrong? | How do I search an error that's not the most recent one? | The AI assistant isn't giving me R-specific answers. How do I fix this? | Can I use searcher in non-interactive scripts?

Introduction | What are Prompts? | The Prompt Management System | Built-in Prompt Library | Setting an Active Prompt | Using Custom Prompts | Checking and Clearing Prompts | Extending the Prompt Library | Removing Prompts | Advanced Usage | Prompt Layering | Creating a Session Prompt Library | Prompt Management in .Rprofile | Conclusion

Introduction | Available AI Services | Basic Usage | AI Service Links | Links Used by the Package | Account Requirements | Customizing AI Behavior with Prompts | 1. Per-call Prompts | 2. Default Prompts via Options | Error Handling Integration | Effective Prompting Strategies | Understanding Prompts | Tailoring Prompts to Different AI Services | Debugging Code | Learning New Concepts | Selecting Packages and Tools | Code Review and Improvement | More effective prompt | Complex Statistical Analysis | Creating Visualizations | Experimenting with Different Approaches | Advanced Prompt Management | Conclusion

Introduction | Usage | Search Operators | General Search Tips | Search Platform URLs | Search Engines | Community Sites | Code Repositories | URL Construction

Introduction | Setup and Authentication | Managing Repositories | Listing Repositories | Listing Organizations | Working with Files | Getting File Content | Creating or Updating Files | Deploying Files Across Repositories | Direct File Deployment | Creating Pull Requests | Advanced Use Cases | Deploying Files with Directory Structure | Dry Run Mode | Filtering and Targeting Repositories | Recommendations | Deployment Script Example | Fin

Overview | Linear Regression | Two-Step Implementation | Verifying Results

Overview | Usage | Error Search | Warning Search

Intro | Functions | Data

What is sitmo and can I eat it? | Accessing and using engines in sitmo | Construct an engine | Seed modifiers | Misc Seed | Examples | Hello World Example | Setting a Seed | Reset RNG engine | Two RNG Streams | Uniform Random Number Generator | OpenMP Example

Introduction | Results of the Test

Overview | Templates | Beamer | beamer_illinois | beamer_orange | beamer_mil | beamer_imetropolis | HTML | html_imetropolis

Intro | Data | Constructing the Model Matrix | Modeling the Data | Parameter Estimates

Intro | Simulation | Simulation Results | Exporting Results for Publication

Overview | Notation | Usage | Matrix Simulation | Identifiable Q Matrix Simulation | $\eta$ Matrix Simulation | Attribute profile simulation | DINA Simulation | DINA Item Simulation | DINA Attribute Simulation | rRUM Simulation | Simulate rRUM items

Package usage | R Package Usage | C++ Usage | C++ Standalone Usage | C++ Package

Supported Colour Maps | Organisation of Colour Maps | Colour Maps | Linear | Diverging | Rainbow | Cyclic | Isoluminant | Overall

Intro | Random Uniform Distribution (runif) in C++ | Creating a Random Uniform Distribution

Installation of rgen | Using rgen | Standalone file usage | Package usage