[TRI-1333] : Upgrade all packages to use Node18 and use fetch instead node-fetch

[Rutam21]

Closes #525

✅ Checklist

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

---

Testing

Typechecking for the Packages folder has been done as mentioned in the ticket.

pnpm run --filter "./packages/**" typecheck

Smoke Testing has been done as suggested by @ericallam .

• Events and Delays jobs were run using pnpm run events/delay. The commands executed succesfully and the jobs started listening on Port 8080.

• Then the triggers were run using pnpm run dev trigger that refreshed the job catalog on the Trigger Cloud dashboard.

• If any changes were made in the code to either enable or disable a particular job, the trigger kept refreshing the job catalog.

• Job were properly listed on the Jon dashboard on Trigger Cloud.

• Jobs were tested on the Cloud Dashboard and were running successfully.

• pnpm run --filter "!./apps/**" typecheck was also run in the root to make sure the types are in-tact.

---

Changelog

• All the Packages are updated to use the Node v18.0.0 LTS from now on.
• Minor fixes are done to support fetch and its available functions.
• Node-Fetch imports and dependency are removed in all packages and fetch is getting used as the native function as supported by Node 18 now.

---

Note: Changeset has been added as a Patch release only.

[changeset-bot]

🦋 Changeset detected

Latest commit: 34809d3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 36 packages

Name	Type
@trigger.dev/integration-kit	Minor
@trigger.dev/eslint-plugin	Minor
@trigger.dev/sdk	Minor
@trigger.dev/sveltekit	Minor
@trigger.dev/express	Minor
@trigger.dev/nestjs	Minor
@trigger.dev/nextjs	Minor
@trigger.dev/astro	Minor
@trigger.dev/core	Minor
@trigger.dev/cli	Minor
@references/nextjs	Patch
@trigger.dev/testing	Minor
astro-example	Patch
@references/job-catalog	Patch
nestjs-example	Patch
@references/package-tester	Patch
@references/remix	Patch
svelte-example	Patch
@references/unit-testing	Patch
perf	Patch
@trigger.dev/tailwind-config	Minor
@trigger.dev/tsconfig	Minor
@trigger.dev/react	Minor
@trigger.dev/remix	Minor
@trigger.dev/airtable	Minor
@trigger.dev/github	Minor
@trigger.dev/linear	Minor
@trigger.dev/openai	Minor
@trigger.dev/plain	Minor
@trigger.dev/replicate	Minor
@trigger.dev/resend	Minor
@trigger.dev/sendgrid	Minor
@trigger.dev/slack	Minor
@trigger.dev/stripe	Minor
@trigger.dev/supabase	Minor
@trigger.dev/typeform	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Rutam21]

@ericallam Please review and suggest changes, if any. Thanks.

[ericallam]

At first glance this is looking good. Will try and find time over the weekend to review but will get to it by Monday latest 👍

[ericallam]

Pulled this down and looks like there is an issue with the pnpm-lock.yaml file as I'm getting this error when running pnpm install:

Ignoring broken lockfile at /Users/eric/code/triggerdotdev/trigger.dev: Lockfile /Users/eric/code/triggerdotdev/trigger.dev/pnpm-lock.yaml not compatible with current pnpm

Can you make sure you are using [email protected]

[Rutam21]

@ericallam I have updated the pnpm.lock file as per pnpm v7.18.1. My curent system pnpm is also set to 7.18.1.

Please review and suggest changes, if any. Thank you.

[ericallam]

Unfortunately because of the original usage of pnpm v8, when you ran pnpm install with pnpm v7 in this branch it caused a complete re-creation of the pnpm-lock.yaml file, resulting in massive changes to the dependencies that are installed (basically as if there was no pnpm-lock.yaml file to begin with). To be able to merge this PR more quickly I would suggest reverting all changes made to the pnpm-lock.yaml file from the beginning of these PR and re-run pnpm install, starting from the last known good point. One way you could do that is grabbing the contents of pnpm-lock.yaml from the commit just before your commits and copy/pasting into your local pnpm-lock.yaml file and then running pnpm install and then committing/pushing.

[Rutam21]

@ericallam Thanks for the suggestion. I grabbed the lock file from the main branch of my fork from which this PR branch was created and then did a pnpm i and pushed the updated the lock file back. Hope this resolves all the previous version conflicts.