Add `INNGEST_API_BASE_URL` and `INNGEST_EVENT_API_BASE_URL`

inngest / inngest-js

The developer platform for easily building reliable workflows with zero infrastructure for TypeScript & JavaScript

https://www.inngest.com/

GNU General Public License v3.0

414 stars 41 forks source link

Add `INNGEST_API_BASE_URL` and `INNGEST_EVENT_API_BASE_URL` #378

Closed jpwilliams closed 11 months ago

jpwilliams commented 11 months ago

Summary

In addition to INNGEST_BASE_URL, adds INNGEST_API_BASE_URL and INNGEST_EVENT_API_BASE_URL.

No current users should have to use this, but this is useful for our own internal testing.

Checklist

[ ] ~~Added a docs PR that references this PR~~ N/A Internal
[ ] ~~Added unit/integration tests~~ N/A
[x] Added changesets if applicable

changeset-bot[bot] commented 11 months ago

🦋 Changeset detected

Latest commit: 02a15984db248f69938c3938ded007ef4754d0cf

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

This PR includes changesets to release 1 package

| Name | Type | | ------- | ----- | | inngest | Patch |

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

inngest-release-bot commented 11 months ago

A user has added the prerelease/inngest label, so this PR will be published to npm with the tag pr-378. It will be updated with the latest changes as you push commits to this PR.

You can install this prerelease version with:

npm install inngest@pr-378

The last release was built and published from 02a15984db248f69938c3938ded007ef4754d0cf.

djfarrelly commented 11 months ago

My only thought and open question - should it be INNGEST_API_... and INNGEST_EVENT_API... or just INNGEST_EVENT...? 🤔