Skip to content
This repository was archived by the owner on Aug 3, 2025. It is now read-only.

Conversation

tobinbc
Copy link

@tobinbc tobinbc commented May 26, 2023

Currently if you do not have a .env and do not use any env fields in next.config.js the component causes a full JS / rendering error in the browser, because process.env will not be defined at all.

Added a try catch for extracting the id from env or from the props.

Prompted because I am using publicRuntimeConfig instead of env.

Would also help with #451

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant