fix(community): Fix handling of ChromeAI chunks #7700
Merged
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.
Trying to use
ChromeAI
with Chrome 133 (Version 133.0.6943.99 (Official Build) (arm64)
) on MacOS seems to be giving very weird results:Using the fix proposed in this PR (with
patch-package
locally to test more easily):It's not clear if something changed in a later version of Chrome? It looks like it could be related to the new 133 release, since it was working fine with 132 before.
Below is a minimal app to reproduce the issue:
package.json
main.js
index.html