tauri-app-sidecar-nodejs

When to use this skill

ALWAYS use this skill when the user mentions:

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

Trigger phrases include:

• "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
• 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

tauri sidecar, nodejs, packaging, lifecycle

Common Gotchas

1. Version compatibility: Pay attention to compatibility between framework versions and dependency libraries; APIs may differ across versions.
2. Configuration file format: Configuration file format errors are 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, and do not hardcode sensitive information.
4. Dependency conflicts: When multiple versions coexist, pay attention to dependency conflicts and use lock files to pin versions.
5. Performance pitfalls: In large data volume scenarios, pay attention to performance optimization and avoid common issues such as N+1 queries.

Usage workflow

Step 1: Environment preparation

Ensure the necessary dependencies and tools are installed in the development environment.

Step 2: Configuration initialization

Perform basic configuration according to project requirements.

Step 3: Using core functionality

Implement the core functionality according to the example code.

Step 4: Test verification

Run tests to ensure the functionality works properly.

Step 5: Deployment and release

After completing development, proceed with deployment and monitoring.