-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The lastest version will cause the error occured in build,please pay attention to it #112
Comments
I have encountered the same problem. |
@lichuyuan224 @erenard Seems like I have figured out the issue, and its for some reason with the optional chaining I introduced with latest changes. I will try to solve it soon and release a build. I generally test with the node example and things worked out fine and I assumed it was all fine, but doesnt seem to be the case. Sorry about this. |
Seems like this is not the only issue, even version updates to deps has sprung up some other issues, which I am trying to figure out. If either of you have some experience with bundling in JS, that would be a great help. |
I remembered this issue toji/gl-matrix#439 (comment), just #FYI. |
Unfortunately, I'm experiencing the same error described in the first post. Will this be fixed? |
@pdziak I have had tried several ways to fix it, but for some reason, it isnt getting fixed, probably due to my lack of knowledge of module bundlers. Any help would be highly appreciated. |
Guys, I have finally figured out a fix, which was basically a revert on 2 package updates I did, I have no clue how to make it run with the new upgrades, but this new version - v1.3.2 of html-to-docx should work with react just like how it did earlier for you. I apologize for the inconvenience caused. Also I am closing this issue, since its a non-issue, but feel free to re-open it, if someone is still facing this issue. |
The text was updated successfully, but these errors were encountered: