Closed fomachanyade closed 1 year ago
I'm not sure what the issue is here, especially with the error message. React is definitely imported in the LexicalErrorBoundary
. Can you add a reproducible sandbox?
Closing for now due to lack of reproducibility. React is definitely imported in the offending component.
After i changed LexicalErrorBoundary
to my own one, it worked.
If I have spare time this weekend, iI will reproduce failed one and succeeded one.
description
Thank you for contributors in advance.
My team adapt Lexical for collaborative text edit.
Now, I am trying to update lexical version from 0.3.5 to 0.7.6 (current latest), and faced a problem(rest is fine!).
The editor has a feature that uses can paste an image. Inside editor,
INSERT_IMAGE_COMMAND
invoked and fires API request that uploads the image to S3 and return url.This feature worked fine, but after update Lexical version to the latest, It causes below error only at staging environment on Heroku (where NODE_ENV is production).
After spending several hours for debugging, I found that this error causes at API request point, but its response is
201
and OK(confirmed at dev tool network tab).My
Image_plugin.tsx
imported React, so I have no idea about what happened.Any Advises are welcomed.
Below is small reproduction.
editor.tsx
image_plugin.tsx
Lexical version: 0.7.6
Steps To Reproduce
1. 2.
Link to code example:
The current behavior
causes Reference error
The expected behavior
causes no error or show more detailed messages