Add notice on sideEffects in deployment guide

[zcesur]

✅ Checklist

• I have followed every step in the contributing guide
• The PR title follows the convention.
• I ran and tested the code works

---

Changelog

Added an extra step prompting users to include ./src/jobs/**/*.ts in sideEffects if needed

I might have an unconventional monorepo setup since noone else seems to have this issue 🤷‍♂️ But only after doing this did I manage to convince Next.js to not tree shake away my jobs

---

Screenshots

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6418622

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.

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

[ericallam]

Interesting... I wonder if you could share a little more of your file structure and contents so we can track down why this wasn't working. Could you share the contents of the trigger API route file?

[zcesur]

Here ya go:

// apps/console/src/pages/api/trigger.ts
import { createPagesRoute } from "@trigger.dev/nextjs";

import { client } from "~/jobs";

const { handler, config } = createPagesRoute(client);
export { config };

export default handler;


// apps/console/src/jobs/client.ts
import { Trigger } from "@algora/trigger";
export const client = Trigger.init();


// packages/trigger/src/client.ts
import { TriggerClient } from "@trigger.dev/sdk";
// ...
export const init = () =>
  new TriggerClient({
    id: id,
    apiKey: env.TRIGGER_API_KEY,
    apiUrl: env.TRIGGER_API_URL,
  });

I had also made a dummy project as I was trying to track this down. Just pushed it on Github if you wanna reproduce the issue:
https://github.com/zcesur/trigger-sideeffects-repro