How to include packages dependencies (turborepo) | Trigger.dev | Page 1

terse nexus Mar 1, 2025, 5:32 AM

#

We recently refactor our turborepo, our react-email templates live inside @repo/transactional (packages dir).

When trying to deploy our tasks we get:

◒  Building trigger code◐  Building trigger code◓  Building trigger code◑  Building trigger code◒  Building trigger code◐  Building trigger code◓  Building trigger code◑  Building trigger code◒  Building trigger code.◐  Building trigger code.◓  Building trigger code.◑  Building trigger code.◒  Building trigger code.◐  Building trigger code.◓  Building trigger code.◑  Building trigger code.◒  Building trigger code..◐  Building trigger code..◓  Building trigger code..X Error: Build failed with 5 errors:
src/libs/resend.tsx:1:31: ERROR: Could not resolve "@repo/transactional/emails/guide-reminder"
src/libs/resend.tsx:2:33: ERROR: Could not resolve "@repo/transactional/emails/house-monitoring"
src/libs/resend.tsx:3:24: ERROR: Could not resolve "@repo/transactional/emails/sign-up"
src/libs/resend.tsx:4:38: ERROR: Could not resolve "@repo/transactional/emails/site-monitoring-hidden"
src/libs/resend.tsx:5:43: ERROR: Could not resolve "@repo/transactional/emails/site-monitoring-republished"

dull steepleBOT Mar 1, 2025, 5:32 AM

#

Hi @terse nexus. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

To resolve the issue you're experiencing with your turborepo setup and the deployment of your tasks, you need to ensure that the dependencies from your @repo/transactional package are properly included in the build process. Here are a few approaches you can try:

Use the additionalFiles extension:
You can use the additionalFiles build extension to include the necessary files from your @repo/transactional package. Add this to your trigger.config.ts file:
```
import { defineConfig } from "@trigger.dev/sdk/v3";
import { additionalFiles } from "@trigger.dev/build/extensions/core";

export default defineConfig({
  project: "<project ref>",
  build: {
    extensions: [
      additionalFiles({ files: ["packages/transactional/emails/**"] }),
    ],
  },
});
```
This will copy the email templates from your @repo/transactional package to the build directory. Make sure to adjust the path according to your project structure.

Source: The trigger.config.ts file

Use the additionalPackages extension:
If your @repo/transactional package is published (even if just locally), you can use the additionalPackages extension to include it in the build:

import { defineConfig } from "@trigger.dev/sdk/v3";
import { additionalPackages } from "@trigger.dev/build/extensions/core";

export default defineConfig({
  project: "<project ref>",
  build: {
    extensions: [additionalPackages({ packages: ["@repo/transactional"] })],
  },
});

Source: The trigger.config.ts file

#

Custom build extension:
If the above solutions don't work, you might need to create a custom build extension to handle your specific monorepo setup. Here's an example of how you might start:

import { defineConfig } from "@trigger.dev/sdk/v3";
import { BuildExtension } from "@trigger.dev/build";

function monorepoExtension(): BuildExtension {
  return {
    name: "monorepo-extension",
    onBuildStart: async (context) => {
      // Add logic here to copy or symlink your @repo/transactional files
      // You might use Node.js fs methods or shell commands via context.exec
    },
  };
}

export default defineConfig({
  project: "<project ref>",
  build: {
    extensions: [monorepoExtension()],
  },
});

Source: Build extensions

Remember to install the @trigger.dev/build package in your devDependencies if you haven't already:

npm add @trigger.dev/build@latest -D

After implementing one of these solutions, try deploying your tasks again. If you're still encountering issues, you might need to adjust the import paths in your `src/libs/resend.tsx` file to match the new structure of your built project.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

terse nexus Mar 1, 2025, 5:33 AM

#

How to include packages dependencies (turborepo)

dull steepleBOT Mar 1, 2025, 5:33 AM

#

@terse nexus Kapa.ai is still learning and improving, please let me know how I did by reacting below.

dusty sand Mar 1, 2025, 1:31 PM

#

Where are your trigger tasks in your monorepo? In general what is the structure of the repo? Have you got a tsconfig which has the paths set for @repo/transactional?

terse nexus Mar 2, 2025, 1:55 PM

#

Hi Matt,

apps/api has this resend lib (each of these functions runs as a individual trigger.dev task) that uses react-email templates that we have extracted to @repo/transactional.

api > package.json
"dependencies": {
  "@repo/transactional": "workspace:*",
  ...
}

#

#

packages > transactional > package.json

terse nexus Mar 2, 2025, 8:19 PM

#

The issue should be that we need to add a build step to the workflow I guess

#

dusty sand Mar 3, 2025, 11:57 AM

#

What's in your tsconfig file where your trigger tasks live (e.g. app)?

I'm pretty sure that error is when TypeScript can't locate the module. Claude:

This error message suggests that your TypeScript compiler can't find the module ⁠@repo/transactional/emails/guide-reminder that's being imported in your ⁠src/libs/resend.tsx file. This is indeed often related to TypeScript path configuration issues. Let me help you troubleshoot this.
The error typically occurs when:
    1.    Your ⁠tsconfig.json doesn't have proper path mappings for the ⁠@repo namespace
    2.    The module actually doesn't exist at the specified location
    3.    There's a mismatch between your import path and the actual file structure
Let me search for some specific information about TypeScript path configurations and this type of error to give you a more targeted solution.

terse nexus Mar 3, 2025, 1:28 PM

#

The odd thing here is that we can deploy locally, what breaks is the github workflow for deploying tasks:

#

#

We've added a build step

#

And we also introduced rollup to bundle the package (@repo/transactional )

#

This is the new error we are getting

dusty sand Mar 3, 2025, 3:34 PM

#

Oh interesting, if it’s only happening in GitHub actions then it’s probably a working directory issue

#

Which folder do you deploy from locally?

terse nexus Mar 4, 2025, 1:52 PM

#

If we remove the build step and this package from the equation, it works hehe

#

The workflow I mean

#

It's the same workflow we've been using for almost a year

dusty sand Mar 4, 2025, 2:02 PM

#

But this works locally when deploying just not using GH actions?

#

If you run the deploy command locally from a subdirectory then you might need to specify the step to use that:

name: Deploy to Trigger.dev (prod)

on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v4

      - name: Use Node.js 20.x
        uses: actions/setup-node@v4
        with:
          node-version: "20.x"

      - name: Install dependencies
        working-directory: ./app
        run: npm install

      - name: 🚀 Deploy Trigger.dev
        working-directory: ./app
        env:
          TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
        run: |
          npx trigger.dev@latest deploy

Note the working-directory

terse nexus Mar 4, 2025, 10:17 PM

#

Exactly it's only the gh action for deploying that is breaking. We can deploy locally.

#

I believe this should work?

#

It's a turborepo

terse nexus Mar 5, 2025, 4:22 AM

#

Is there a way to get to the logs somehow? That would be helpful

#

I have the feeling that the dist files after the build step are not reachable

dusty sand Mar 5, 2025, 2:58 PM

#

If you do -l debug it will spit out a ton of logs inline

#

The most common reason CI doesn't work (but it works locally) is the worker directory. I'm not sure what other issues could cause this.

terse nexus Mar 5, 2025, 7:16 PM

#

Ok thank you

dusty sand Mar 5, 2025, 7:26 PM

#

Hopefully the bottom of the verbose logs will be helpful

terse nexus Mar 6, 2025, 5:45 PM

#

#17 2.074 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@repo%2ftransactional - Not found
#17 2.075 npm ERR! 404 
#17 2.075 npm ERR! 404  '@repo/[email protected]' is not in this registry.
#17 2.075 npm ERR! 404 
#17 2.075 npm ERR! 404 Note that you can also install from a
#17 2.075 npm ERR! 404 tarball, folder, http url, or git url.
#17 2.076

#

I'm not sure why it's not being included

dusty sand Mar 6, 2025, 5:55 PM

#

Huh, it thinks it's a public package

#

How do you reference it in your package.json? Do you use pnpm?

#

We use pnpm and do stuff like this:

"dependencies": {
  "ioredis": "^5.3.2",
  "@trigger.dev/core": "workspace:*"
},

terse nexus Mar 6, 2025, 6:13 PM

#

Exactly

#

We do it like that

#

We use pnpm as well

#

#

dusty sand Mar 6, 2025, 6:25 PM

#

Wtf this makes no sense

#

This is very common for people to do using us 🤔

#

I assume this is you? https://stackoverflow.com/questions/79490316/using-local-packages-in-github-actions-with-pnpm-workspace

Stack Overflow

Using Local Packages in GitHub Actions with pnpm Workspace

Problem
I have a monorepo using turborepo and pnpm workspaces. Inside it, there's an internal package @repo/transactional that contains email templates. When I run a GitHub Actions workflow that de...

#

Good extra details in that SO post

#

@karmic river any ideas what's going on here?

karmic river Mar 6, 2025, 6:39 PM

#

Not at computer, but doing a dry run would be the first step

terse nexus Mar 6, 2025, 6:44 PM

#

dusty sand I assume this is you? https://stackoverflow.com/questions/79490316/using-local-p...

Yes that's me

terse nexus Mar 6, 2025, 6:47 PM

#

dusty sand Wtf this makes no sense

Yepp I'm not sure what's going on here xD

dusty sand Mar 6, 2025, 6:49 PM

#

This only happens on GitHub Actions? Locally it works perfectly?

#

To do a dry run you add this at the end of the deploy command --dry-run. But not sure how you'll get the output from CI.

#

If it works locally. Can you try deleting all the .trigger folders (they're build caches). Then try deploy again from local

terse nexus Mar 6, 2025, 6:53 PM

#

"If it works locally. Can you try deleting all the .trigger folders (they're build caches). Then try deploy again from local"

Trying this now

#

Now it fails locally as well

#

At least I can reproduce locally now

#

Thanks for the tip!

dusty sand Mar 6, 2025, 6:57 PM

#

Ok good. Try doing --dry-run

#

It'll spit out a folder and you can take a look at it to try figure out what's going wrong

terse nexus Mar 6, 2025, 6:57 PM

#

Thank you!

terse nexus Mar 6, 2025, 10:02 PM

#

#

#

#

It looks like it's all there

#

terse nexus Mar 6, 2025, 10:08 PM

#

terse nexus

This is the code that's in "@repo/transactional"

#

We can deploy our api to fly.io (docker) without complaints

#

#

This is the container file that runs

#

Could this line be the issue?

RUN npm i --no-audit --no-fund --no-save --no-package-lock

That it uses npm instead over pnpm and hence it does not understand the pnpm workspace structure?

karmic river Mar 7, 2025, 9:12 AM

#

terse nexus This is the container file that runs

It's not because we're using npm, it's because @repo/transactional isn't a published package but you are trying to install it via npm

#

Have you added that package to external in the trigger config file?

karmic river Mar 7, 2025, 10:06 AM

#

Might be easier to debug this via screenshare

terse nexus Mar 7, 2025, 2:22 PM

#

Hi Eric,

We tried to add @repo/transactional to external, without success

#

Sure, please let me know when you are available

#

Many thanks in advance

karmic river Mar 7, 2025, 5:13 PM

#

Don't add it to external is my point, it should be bundled

karmic river Mar 7, 2025, 5:13 PM

#

terse nexus Sure, please let me know when you are available

What's your trigger.config.ts file look like?

terse nexus Mar 7, 2025, 5:13 PM

#

It's not there any more

karmic river Mar 7, 2025, 5:13 PM

#

Also in the future if you reply to me in here it's better to reply to a specific message so I get alerted, otherwise I miss the message

#

But it's still getting added to the package.json when doing --dry-run?

terse nexus Mar 7, 2025, 5:14 PM

#

karmic river What's your trigger.config.ts file look like?

Here's our config

karmic river Mar 7, 2025, 5:17 PM

#

terse nexus Here's our config

Can you do a --dry-run deploy with the --log-level debug flag, and send me in a DM the contents of the dry run output, as well as the full output of the logs?

terse nexus Mar 7, 2025, 5:38 PM

#

karmic river Can you do a `--dry-run` deploy with the `--log-level debug` flag, and send me i...

I sent you the logs in a dm, when I run --dry-run together with --log-level debug I don't get any path to a specific log file (I just get the output from the cli), but when I run --log-level debug without --dry--run I get a path to build logs (I included this)

karmic river Mar 7, 2025, 5:54 PM

#

terse nexus I sent you the logs in a dm, when I run --dry-run together with --log-level debu...

👍

radiant oracle Mar 15, 2025, 11:30 AM

#

@dull steeple does trigger.cofig.ts project takes env

dull steepleBOT Mar 15, 2025, 11:30 AM

#

Let me check the knowledge base for you again. One moment! :books:

#

Yes, the project field in your trigger.config.ts file can use environment variables. Instead of hardcoding your project reference, you can use an environment variable like this:

import { defineConfig } from "@trigger.dev/sdk/v3";

export default defineConfig({
  project: process.env.TRIGGER_PROJECT_REF || "<project ref>",
  // Your other config settings...
});

This approach is useful when you want to deploy to different projects based on your environment (e.g., development, staging, production).

When running the CLI commands, you can provide the environment variable in several ways:

Using the --env-file flag with the CLI:
```
npx trigger.dev@latest dev --env-file .env
```
CLI dev command
Setting the environment variable in your terminal before running the command.
Using environment variables from your deployment platform, which can be synced to Trigger.dev using build extensions like syncVercelEnvVars or syncEnvVars.
Sync env vars

This approach gives you flexibility when working with different environments or CI/CD pipelines.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@radiant oracle Kapa.ai is still learning and improving, please let me know how I did by reacting below.

radiant oracle Mar 15, 2025, 11:33 AM

#

@dull steeple this is not getting pouplated process.env.TRIGGER_PROJECT_REF instead the string is used

dull steepleBOT Mar 15, 2025, 11:33 AM

#

Let me check the knowledge base for you again. One moment! :books:

#

I understand the issue you're facing - your environment variable process.env.TRIGGER_PROJECT_REF isn't being populated in the trigger.config.ts file, and instead, the literal string is being used.

This is a common issue with the build process. The trigger.config.ts file is processed during build time, and environment variables need to be properly set up to be available during this phase.

Here are a few approaches to solve this:

Make sure your environment variable is available during the build process. You can check if it's properly set in your environment by adding a console log in your config file:

console.log("TRIGGER_PROJECT_REF:", process.env.TRIGGER_PROJECT_REF);

If you're using the Trigger.dev CLI, make sure you're providing the environment file:

npx trigger.dev@latest dev --env-file .env

For environment variables that need to be available at runtime in your deployed tasks, you should use the environment variables management features of Trigger.dev:

You can add environment variables through:

The Trigger.dev dashboard in the "Environment Variables" page
Using the syncEnvVars build extension
Using the syncVercelEnvVars extension if you're using Vercel

Sync env vars from another service

For local development, make sure your .env file contains the TRIGGER_PROJECT_REF variable and that it's being loaded properly.

If you continue to have issues, you might need to hardcode the project ref for the config file specifically, while using environment variables for your actual task code.

Let me know if you need more specific guidance based on your setup!

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@radiant oracle Kapa.ai is still learning and improving, please let me know how I did by reacting below.

#How to include packages dependencies (turborepo)

After implementing one of these solutions, try deploying your tasks again. If you're still encountering issues, you might need to adjust the import paths in your src/libs/resend.tsx file to match the new structure of your built project.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

This approach gives you flexibility when working with different environments or CI/CD pipelines.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

Let me know if you need more specific guidance based on your setup!

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

After implementing one of these solutions, try deploying your tasks again. If you're still encountering issues, you might need to adjust the import paths in your `src/libs/resend.tsx` file to match the new structure of your built project.