search

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

[BUG] No signing key warning spam in development #356

Closed ianschmitz closed 10 months ago

ianschmitz commented 11 months ago

Describe the bug After the change in https://github.com/inngest/inngest-js/pull/125, our console now gets a lot of warning messages of the following:

No signing key provided to validate signature. Find your dev keys at https://app.inngest.com/test/secrets

Reading the PR, i see this looks to be an intentional change. However it's quite spammy in development and covers up other possible legitimate error messages i might be missing from Next.

To Reproduce Steps to reproduce the behavior:

  1. Use the SDK as intended in a local development environment

Expected behavior Not to spam my console during local development when using the SDK as intended.

Code snippets / Logs / Screenshots

image

System info (please complete the following information):

Additional context

transitive-bullshit commented 11 months ago

This is really confusing for a new dev coming in.

jpwilliams commented 10 months ago

This fixed in 3.4.4.