Skip to content
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

Getting errors on converting the html to docx #55

Open
Hariharan-5c opened this issue Jan 23, 2025 · 2 comments
Open

Getting errors on converting the html to docx #55

Hariharan-5c opened this issue Jan 23, 2025 · 2 comments

Comments

@Hariharan-5c
Copy link

We are encountering runtime errors with the @turboxhtml-to-docx library in our production environment using Node.js version 20. Surprisingly, these errors do not occur in our testing environment, which also uses Node.js version 20.

Error Logs

/app/build/node_modules/@turbodocx/html-to-docx/dist/html-to-docx.umd.js
at convertHTML (/app/build/node_modules/html-to-vdom/lib/html-to-vdom.js
/app/build/node_modules/html-to-vdom/lib/html-to-vdom.js
var getVNodeKey = hasOptions ? options.getVNodeKey : undefined;
@nicolasiscoding
Copy link
Member

Hi @Hariharan-5c , thanks for sharing this.

If you can, can you post the full stack trace? This isn't enough info for us to repro with.

Also can you detail more of the differences between your prod and test environments? Node version is good, but if it's working on one, it should work on the other.

For your own purposes, maybe do a DIFF on the package-lock in testing and prod to see if there are any conflicting dependencies or other libraries/bundling solutions that could be causing this

1 similar comment
@nicolasiscoding
Copy link
Member

Hi @Hariharan-5c , thanks for sharing this.

If you can, can you post the full stack trace? This isn't enough info for us to repro with.

Also can you detail more of the differences between your prod and test environments? Node version is good, but if it's working on one, it should work on the other.

For your own purposes, maybe do a DIFF on the package-lock in testing and prod to see if there are any conflicting dependencies or other libraries/bundling solutions that could be causing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants