-
Notifications
You must be signed in to change notification settings - Fork 87
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
Rollback to module-name import to fix defaults issue #40
Conversation
Local build you mean the sanitize-html installation into the libraries? If so, yes. Using "npm install sanitize-html". |
Afaik, this should work as I tested it locally and also using an npm build. @lucgagan would be nice to have this in sooner cos the main currently breaks. |
@rajeshdavidbabu , can you help me with the steps how you made the local build of the sanitize-html? bcz still am facing the issue. |
Anyone helping me here? |
@prathyusha586-0408 okay this is not yet merged so alternatively you can do the following:
yeah are you using the local auto or the auto from npm ? Go to the file where you use |
Hi folks, Wondering if this fix will be merged soon, I am working on a POC and this tool looks very interesting. Thanks for all your effort! |
Please merge the fix, guys. This is blocker for running tests. |
@lucgagan let me know if there is something wrong with this one. If not we have to merge it inorder to unblock users. |
@rajeshdavidbabu , i have tried as mentioned but getting below error: |
I tried to use auto-playwright but also ran into this issue. What is holding this up? |
@lucgagan When can a new release/npm package version be expected? |
I still can't get this to work out of the box. Like the others, I am getting: TypeError: Cannot read properties of undefined (reading 'defaults') |
I'm also still getting this error. |
I'm still getting this error too |
I've revert the sanitizeHtml.ts import from |
@lucgagan Is this fix going to be release? |
Why ?
Based on the official docs of sanitize-html we need do the following:
Problem:
Fix:
Connected issue
#36