@trigger.dev/sdk 4.5.15 → 4.5.16

package/dist/commonjs/version.js

@@ -1,5 +1,5 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.VERSION = void 0;
-exports.VERSION = "4.5.15";
+exports.VERSION = "4.5.16";
 //# sourceMappingURL=version.js.map

package/dist/esm/version.js

@@ -1,2 +1,2 @@
-export const VERSION = "4.5.15";
+export const VERSION = "4.5.16";
 //# sourceMappingURL=version.js.map

package/docs/config/extensions/custom.mdx

@@ -80,7 +80,7 @@ export default defineConfig({
     extensions: [
       {
         name: "my-extension",
-        externalsForTarget: async (target) => {
+        externalsForTarget: (target) => {
           return ["my-dependency"];
         },
       },
@@ -89,6 +89,19 @@ export default defineConfig({
 });
 ```
 
+### installedPackagesForTarget
+
+This tells build diagnostics which packages your extension installs into the deployed image for a given target, so warnings (like the one for packages loaded via `createRequire()`) don't fire for packages that will actually be available at runtime. The bundler ignores this hook, so declaring it never changes the build output. Only implement it if your extension installs packages; extensions without it are assumed to install none.
+
+```ts
+{
+  name: "my-extension",
+  installedPackagesForTarget: (target) => {
+    return target === "deploy" ? ["my-dependency"] : [];
+  },
+}
+```
+
 ### onBuildStart
 
 This hook runs before the build starts. It receives the `BuildContext` object as an argument.

package/docs/github-integration.mdx

@@ -34,7 +34,7 @@ This eliminates the need to manually run the `trigger.dev deploy` command or set
 <Step title="Customize build settings (optional)">
   Configure how your project is built:
 
-  - **Trigger config file**: Path to your `trigger.config.ts` file. By default, we look for it in the root of your repository. The path should be relative to the root of your repository and contain the config file name, e.g., `apps/tasks/trigger.config.ts`.
+  - **Trigger config file**: Auto-detected by default — we find your `trigger.config.ts` anywhere in your repository. Set a path relative to the root of your repository to override it, e.g., `apps/tasks/trigger.config.ts`. If your repository contains more than one config file, set the path of the one to use.
   - **Install command**: Auto-detected by default, but you can override it if necessary. The command will be run from the root of your repository.
   - **Pre-build command**: Run any commands before building and deploying your project, e.g., `pnpm run prisma:generate`. The command will be run from the root of your repository.
 </Step>

package/docs/troubleshooting.mdx

@@ -87,7 +87,7 @@ Usually there will be some useful guidance below this message. If you can't figu
 
 ### `resource_exhausted`
 
-If you see a `resource_exhausted` error during deploy, the build may have hit resource limits on our build infrastructure. Try our [native builder](https://trigger.dev/changelog/deployments-with-native-builds).
+If you see a `resource_exhausted` error during deploy, the build may have hit resource limits on our build infrastructure. Try our [native builder](https://trigger.dev/changelog/deployments-with-native-builds) by deploying with the `--native-build` flag.
 
 ### `No loader is configured for ".node" files`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trigger.dev/sdk",
-  "version": "4.5.15",
+  "version": "4.5.16",
   "description": "trigger.dev Node.JS SDK",
   "license": "MIT",
   "publishConfig": {
@@ -69,7 +69,7 @@
   "dependencies": {
     "@opentelemetry/api": "1.9.1",
     "@opentelemetry/semantic-conventions": "1.41.1",
-    "@trigger.dev/core": "4.5.15",
+    "@trigger.dev/core": "4.5.16",
     "uncrypto": "^0.1.3"
   },
   "devDependencies": {