Secrets support
See original GitHub issueIs your feature request related to a problem? Please describe.
I’d like to be able to specify API secrets in a StackBlitz project without sharing them publicly. I’m fine with the code being shared publicly (because the repository itself is open-source), but I don’t want to have certain environment variables (e.g. API keys, secret tokens) shared publicly.
Describe the solution you’d like
I’d like to be able to specify secrets in a project’s settings (that are only accessible via process.env
when I’m logged in). Essentially, I just want StackBlitz to have CodeSandbox’s existing secrets feature.
Describe alternatives you’ve considered
I could (if it’s possible) create a private StackBlitz project and then just add the environment variables in a .env.local
file.
Additional context
I’m trying to get Tutorbook working as a StackBlitz project so that I can edit on the go (via any web browser) wherever I am.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:14
Top GitHub Comments
Example code: https://stackblitz.com/edit/node-secrets-example-localstorage-v2?file=localStorageSecrets.js
There’s an ugly workaround for frontend code - put them into localstorage of preview frame.