Core package and move to @latest (#235)

* Changeset should ignore the example projects * Removed note in Contributing instructions about not adding a changeset for internal * Renamed @trigger.dev/internal to @trigger.dev/core. Set sdk and internal to be ES2020, so we don’t get errors about private identifiers * Env vars in nextjs-example use square bracket syntax to avoid Turbo Repo errors * Set the tsconfigs back for core and sdk * @examples/nextjs compile error with undefined tasks * Set the example projects to use ES2015 to avoid private modifier complaints * package-tester example, which will use built packages * package-tester package.json * Created a readme for the package-tester * Added all the packages to package-tester * Create .env.local.example and readme instructions * Added name to the package.json * Upgraded @types/react and @types/react-dom everywhrre, so we can use server actions * Upgraded @types/react and @types/react-dom everywhrre, so we can use server actions * Reworked the react package build, so it generates separate files * The SDK no longer bundles core * package-tester setup with a server action and react hooks * Added new SDK methods with logging * Working tsup settings for client and server * Explicit react hooks return types * Added all the hooks for testing * Added OpenAI step to the job to check types are still ok in integrations * Get rid of rogue Changeset ignores * Changeset: @trigger.dev/core is now a separate package * Exited prerelease mode, added a changeset * Changed @next to @latest * Deleted seed.js, this shouldn’t be committed * Ignore seed.js * The webapp was importing @trigger.dev/core with a folder path rather package name… * More webapp imports instead of @trigger.dev/core were a folder path * Accidentally edited Stripe internal API url in the comment * Added “sideEffects”: false so @trigger.dev/core is tree shaken by Remix
2023-07-31 18:47:34 +01:00
parent efd590976c
commit 92233f2e90
148 changed files with 1378 additions and 740 deletions
@@ -215,7 +215,7 @@ Here's an example of creating a `patch` changeset for the `@trigger.dev/github`

 [![asciicast](https://asciinema.org/a/599228.svg)](https://asciinema.org/a/599228)

-You will be prompted to select which packages to include in the changeset. Only select the packages that you have made changes for (Important: never include a changeset for the `@trigger.dev/internal` package, as it's bundled with other packages and should not be published).
+You will be prompted to select which packages to include in the changeset. Only select the packages that you have made changes for.

 Most of the time the changes you'll make are likely to be categorized as patch releases. If you feel like there is the need for a minor or major release of the package based on the changes being made, add the changeset as such and it will be discussed during PR review.