Eric Allam
f040417440
* Support custom config file names & paths * Fix entry point paths on windows * Support custom conditions Add support for custom conditions (for bundling and running), to support being able to import `ai/rsc` with the “react-server” condition. - Fixed an issue where symlinking unresolvable externals after rebuilding caused the build to hang - Fixed an issue with external not working with subpath exports (e.g. “ai” would not match “ai/rsc”) - Protect better against build extensions breaking builds * Add changeset * Fix passing CLI process.env down to the task processes * Remove unused import * reviving the e2e CLI tests * Another attempt at fixing windows * yet another windows attempt (yawa) * Output index child stdout and stderr (yawa) * normalize import paths for windows * Added some logging (yawa) * normalize the loader path as well * Added some logging to figure out why the entry points aren’t being found on windows * Fix for entry point detection on windows * Normalize runner import loader path * Normalize import paths in dev and make sure rewritten build manifest paths are correct on windows as well * Various cleanup after windows fixes * Remove the webapp e2e for now * Add node10 type resolution support for subpath exports (still does not actually import in Node 10 or Browserify/Parcel) https://github.com/andrewbranch/example-subpath-exports-ts-compat * init using templates again but downloaded from the repo this time * Adding init schedule example * Support for js init * init now working with js * Fix issues with links in terminals that don’t support them. Also skip update check of version starts with 0.0.0
About Trigger.dev
Trigger.dev is an open source platform and SDK which allows you to create long-running background jobs with no timeouts. Write normal async code, deploy, and never hit a timeout.
Features:
- JavaScript and TypeScript SDK
- Write reliable code by default
- No infrastructure to manage
- Works with your existing tech stack
In your codebase
Create tasks where they belong: in your codebase. Version control, localhost, test and review like you're already used to.
import { task } from "@trigger.dev/sdk/v3";
//1. You need to export each task
export const helloWorld = task({
//2. Use a unique id for each task
id: "hello-world",
//3. The run function is the main function of the task
run: async (payload: { message: string }) => {
//4. You can write code that runs for a long time here, there are no timeouts
console.log(payload.message);
},
});
Deployment
Use our SDK to write tasks in your codebase. There's no infrastructure to manage, your tasks automatically scale and connect to our cloud. Or you can always self-host.
Environments
We support Development, Staging, and Production environments, allowing you to test your tasks before deploying them to production.
Full visibility of every job run
View every task in every run so you can tell exactly what happened. We provide a full trace view of every task run so you can see what happened at every step.
Getting started
Visit our docs here for a full guide on how to get started with Trigger.dev.
Self-host
If you prefer to self-host, you can follow our self-hosting guide.
Development
To setup and develop locally or contribute to the open source project, follow our development guide.