tauri-app-sidecar-nodejs

When to use this skill

• Node.js runtime as a sidecar / Node.js sidecar runtime
• Sidecar packaging and lifecycle / sidecar packaging and lifecycle
• Frontend-triggered sidecar execution / frontend-triggered sidecar execution

• "sidecar", "nodejs", "packaging", "lifecycle"
• "sidecar", "Node.js", "packaging", "lifecycle"

How to use this skill

1. Define the Node.js sidecar responsibilities and binary output
2. Configure sidecar packaging per platform
3. Manage start, stop, and logging lifecycle in Rust
4. Validate permissions and release build behavior

Outputs

• Sidecar integration plan / sidecar integration plan
• Packaging and lifecycle checklist / packaging and lifecycle checklist

Scope

• Boundary: Sidecar Node.js integration only
• Key points: Packaging and lifecycle management

References

• https://v2.tauri.app/llms.txt
• https://v2.tauri.app/learn/sidecar-nodejs/
• https://v2.tauri.app/zh-cn/learn/sidecar-nodejs/

Keywords

Gotchas

1. Version Compatibility: Pay attention to compatibility between framework versions and dependent libraries; APIs may vary across different versions
2. Configuration File Format: Incorrect configuration file format is the most common issue; it is recommended to use the editor's syntax checking
3. Environment Variables: Ensure all necessary environment variables are set correctly; do not hardcode sensitive information
4. Dependency Conflicts: Pay attention to dependency conflicts when multiple versions coexist; use lock files to lock versions
5. Performance Pitfalls: Pay attention to performance optimization in large data volume scenarios; avoid common issues such as N+1 queries

Usage Process

Step 1: Environment Preparation

Step 2: Configuration Initialization

Step 3: Core Function Usage

Step 4: Testing and Validation

Step 5: Deployment and Launch