devin latest comments

Author: isshaddad

docs/config/extensions/additionalPackages.mdx

@@ -14,14 +14,15 @@ export default defineConfig({
   project: "<project ref>",
   // Your other config settings...
   build: {
+    // Omit version for auto-resolution; for reproducible builds use e.g. packages: ["wrangler@X.Y.Z"]
     extensions: [additionalPackages({ packages: ["wrangler"] })],
   },
 });
 ```
 
-This allows you to include additional packages in the build that are not automatically included via imports. This is useful if you want to install a package that includes a CLI tool that you want to invoke in your tasks via `exec`. We will try to automatically resolve the version of the package but you can specify the version by using the `@` symbol.
+This allows you to include additional packages in the build that are not automatically included via imports. This is useful if you want to install a package that includes a CLI tool you can invoke in your tasks via `exec`. We will try to automatically resolve the version of the package but you can specify the version by using the `@` symbol.
 
-If you omit the version, the build may use a cached or older resolution. For reproducible builds, pin the exact version (e.g. `wrangler@1.19.0`).
+If you omit the version, the build may use a cached or older resolution. For reproducible builds, pin the exact version (e.g. `wrangler@X.Y.Z`).
 
 ```ts
 import { defineConfig } from "@trigger.dev/sdk";
@@ -31,7 +32,7 @@ export default defineConfig({
   project: "<project ref>",
   // Your other config settings...
   build: {
-    extensions: [additionalPackages({ packages: ["wrangler@1.19.0"] })],
+    extensions: [additionalPackages({ packages: ["wrangler@X.Y.Z"] })],
   },
 });
 ```

docs/troubleshooting.mdx

@@ -50,7 +50,7 @@ And you're using Yarn v1.22 or another package manager, check if you have a `.pn
 If you see "Connection error" when running `trigger login` (or "Failed to create authorization code"), try these in order:
 
 1. **Clear saved auth and retry:** `npx trigger.dev@latest logout`, then `npx trigger.dev@latest login` again. Sometimes an invalid config is cached.
-2. **VPN or firewall:** Disconnect from VPN or check firewall/proxy; try `npx trigger.dev@latest login -l debug` for more detail.
+2. **VPN or firewall:** Disconnect from VPN or check firewall/proxy; try `npx trigger.dev@latest login --log-level debug` for more detail.
 3. **TLS / certificate store:** Node may use a different CA store than your OS (e.g. `curl` works but the CLI fails). Try `export NODE_EXTRA_CA_CERTS=/etc/ssl/cert.pem` (macOS/Linux) then login again, or reinstall Node so it gets updated certs. Behind a corporate proxy or custom CA? Set `NODE_EXTRA_CA_CERTS` to that CA file.
 
 ## Deployment