🐛 Bug Report: Studio onboarding issue on node env present #9022
Description
📜 Description
When following the documentation to get up and running using studio on my first time out, I had a very weird issue where I could not get past the onboarding.
This is due to a /discover call failing with SignatureNotFoundError. After investigating, this is caused by this check that enables hmac headers when the env is not “developement”. Our NODE_ENV is set to … dev.
Initiating the client manually with strictAuthentication: process.env.NODE_ENV !== ‘dev’ fixed it for us.
I’d hapily contribute to the resolution, either by widening what is considered a dev env by the client, or just updating the documentation to reflect that behavior, which I think is warranted to improve first time users (like us) experience with Novu :)
👟 Reproduction steps
- Launch bridge endpoint with a NODE_ENV env variable different from “developement"
- Launch studio
- Connect to studio
All calls of the studio to the bridge after healthcheck will fail without information.
👍 Expected behavior
Either:
- Works on a wider array of NODE_ENVs
- Provide an explicit error in the onboarding screen
- Have the docs reflect that behavior
👎 Actual Behavior with Screenshots
Novu version
Novu SaaS
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
- I checked and didn't find a similar issue
🏢 Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to submit PR?
Yes I am willing to submit a PR!