Skip to main content

Make deploying (bundling) much easier

Feature Request

There are two things that aren't great about deploying at the moment:

  1. You can end up having to add a lot packages to dependencesToBundle.

  2. You need to match the versions between the SDK and the CLI.

We are changing the way we bundle your code so it works without intervention in more situations. Mainly this means changing to use ESM – we are currently using CJS because of one of our dependencies.

We are also going to change to a single package for the CLI and SDK. This means it will be impossible to have version mismatches between them.

Posted by Linear ·
Status: Completed4 comments

Comments4

  • maverickdotdev

    •

    Sep 20, 2024

    Our new build system is out alongside the official release of 3.0. You can read more about it here: https://trigger.dev/blog/beta-to-latest-announcement

  • Anonymous User

    •

    Aug 30, 2024

    Reporting some issue:
    1. the doc give the instruction to move externals to the new build. However, the field is actually external without `s` from the SDK


    2. when trying the new dry-run, the cli forces an update on @trigger.dev/sdk to 3.0.0-beta.56, otherwise the dry-run would fail. I have to add --skip-update-check to make it work

  • mattaitken

    Team•

    Aug 27, 2024

    We have a preview package and docs for our new build system.

    It is far better at bundling your project code together, has support for extensions and much more. Read the docs and try it out here: https://trigger.dev/docs/guides/new-build-system-preview

    Feedback would be great as we move to this being the main CLI in a couple of weeks time.

  • Ian Walter

    •

    Aug 22, 2024

    Will this address my issue?