Fix: Handle undefined window.openai in local developmentFix: Handle undefined window.openai in local development #139
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Running the project locally (
pnpm dev) results in a crash with:This happens because the code assumes
window.openai(part of the ChatGPT Apps SDK) is always available, but it's only present when running inside ChatGPT.Solution
Added null checks and graceful fallbacks:
window.openai.setWidgetStateBehavior
Before
After
Testing
Tested locally with
pnpm dev:The changes are backward compatible and don't affect the ChatGPT environment.- Add null checks for window.openai.setWidgetState in useWidgetState hook
Before this change, running the project locally would crash because the code assumed window.openai (part of the ChatGPT Apps SDK) would always be available. Now the code gracefully handles both environments:
This allows developers to run and test the UI components locally without errors.