chore(docs): add WASM external configuration documentation

[isshaddad]

Adds a WASM block to the External section documenting that WASM packages must be added to the external array in trigger.config.ts.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 608c5e4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The change adds documentation guidance for WebAssembly (WASM) package configuration in the build configuration section. A new dedicated WASM subsection is introduced with a code example demonstrating how to declare external WASM packages in build.external. The external-packages note is updated to expand its scope from mentioning only native binaries to cover both native binaries and WebAssembly packages, replacing previous specific examples.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete; it lacks required sections from the template including Testing, Changelog, and the checklist.	Complete the pull request template by adding Testing steps, a Changelog entry, and confirming checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding documentation about WASM external configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[claude]

PR Review: chore(docs): add WASM external configuration documentation

Summary

This PR adds documentation for configuring WebAssembly (WASM) packages in the external array of trigger.config.ts. This is a helpful addition to the docs.

Feedback

Overall: Looks good! This is a straightforward documentation addition that provides useful guidance for users working with WASM packages.

Minor Suggestions

1. Consider adding a concrete example: The code sample uses "your-wasm-package-name" as a placeholder. It would be more helpful to include a real-world WASM package example (similar to how the native binary section mentions re2, sharp, sqlite3). Some common WASM packages users might encounter:

   • @xenova/transformers (ML models)
   • @ffmpeg/ffmpeg (video processing)
   • @pdfme/pdf-lib or similar PDF libraries

2. Slight redundancy: The new subsection "#### WebAssembly (WASM) packages" includes a code example that is nearly identical to the one in the parent "### External" section. Consider either:

   • Using the concrete example suggestion above to differentiate it, OR
   • Simplifying by just adding a sentence to the existing Note block without the full code example

3. Note block improvement: The updated Note at the end is good, but "WASM packages" at the end is a bit generic. Consider listing a specific example: "For example, re2, sharp, sqlite3, and WASM packages like @xenova/transformers should be added to external."

No Issues Found

• ✅ Documentation structure follows existing patterns (h4 subsection under h3 "External")
• ✅ Code example syntax is correct
• ✅ Explanation is technically accurate
• ✅ No security concerns for documentation changes

Overall this is a helpful documentation improvement. The suggestions above are optional polish - feel free to merge as-is if you prefer the current approach.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/config/config-file.mdx (1)

451-465: Consider using a concrete WASM package example.

The placeholder your-wasm-package-name is functional, but a real-world example (e.g., tiktoken, argon2, or @xenova/transformers) would make the documentation more immediately actionable for users.

📝 Suggested improvement

   build: {
-    external: ["your-wasm-package-name"],
+    external: ["tiktoken"],
   },

📜 Review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 768206c and 608c5e4.

📒 Files selected for processing (1)

• docs/config/config-file.mdx

🧰 Additional context used

🧠 Learnings (11)

📓 Common learnings

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger.config.ts : Configure build process in trigger.config.ts using `build` object with external packages, extensions, and JSX settings

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger.config.ts : Use build extensions in trigger.config.ts (additionalFiles, additionalPackages, aptGet, prismaExtension, etc.) to customize the build

📚 Learning: 2025-11-27T16:27:35.304Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger.config.ts : Configure build process in trigger.config.ts using `build` object with external packages, extensions, and JSX settings

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2025-11-27T16:27:35.304Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger.config.ts : Use build extensions in trigger.config.ts (additionalFiles, additionalPackages, aptGet, prismaExtension, etc.) to customize the build

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2025-11-27T16:27:35.304Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger/**/*.{ts,tsx,js,jsx} : Use `trigger.dev/sdk/v3` for all imports in Trigger.dev tasks

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2025-11-27T16:26:37.432Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-11-27T16:26:37.432Z
Learning: Applies to packages/trigger-sdk/**/*.{ts,tsx} : In the Trigger.dev SDK (packages/trigger-sdk), prefer isomorphic code like fetch and ReadableStream instead of Node.js-specific code

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2025-11-27T16:27:35.304Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger/**/*.{ts,tsx,js,jsx} : Use the `task()` function from `trigger.dev/sdk/v3` to define tasks with id and run properties

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2025-11-27T16:26:58.661Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/webapp.mdc:0-0
Timestamp: 2025-11-27T16:26:58.661Z
Learning: Applies to apps/webapp/**/*.{ts,tsx} : When importing from `trigger.dev/core` in the webapp, use subpath exports from the package.json instead of importing from the root path

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2025-11-27T16:27:35.304Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger.config.ts : Configure Trigger.dev project in `trigger.config.ts` using `defineConfig()` with project ref and task directories

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2026-01-12T11:01:34.777Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-01-12T11:01:34.777Z
Learning: Applies to **/*.{ts,tsx,js} : Always import task definitions from trigger.dev/sdk, never from trigger.dev/sdk/v3 or deprecated client.defineJob pattern

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2026-01-12T11:01:34.777Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-01-12T11:01:34.777Z
Learning: Applies to **/*.{ts,tsx} : Every Trigger.dev task must be exported; use task() function with unique id and run async function

Applied to files:

• docs/config/config-file.mdx

📚 Learning: 2025-11-27T16:27:35.304Z

Learnt from: CR
Repo: triggerdotdev/trigger.dev PR: 0
File: .cursor/rules/writing-tasks.mdc:0-0
Timestamp: 2025-11-27T16:27:35.304Z
Learning: Applies to **/trigger/**/*.{ts,tsx,js,jsx} : Use `tasks.trigger()` with type-only imports to trigger tasks from backend code without importing the task implementation

Applied to files:

• docs/config/config-file.mdx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

docs/config/config-file.mdx (1)

467-470: LGTM!

The updated Note correctly expands the guidance to cover both native binaries and WASM packages, providing clear examples for each category.