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

Ignore stderr punycode deprecation warning #188

Closed
alfonsrv opened this issue Jun 9, 2024 · 2 comments
Closed

Ignore stderr punycode deprecation warning #188

alfonsrv opened this issue Jun 9, 2024 · 2 comments

Comments

@alfonsrv
Copy link

alfonsrv commented Jun 9, 2024

Cannot use this anymore due to the (node:60710) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead. error. I tried working around this, but found out mjml itself depends on libraries directly linked to punycode (see mjmlio/mjml#2843)

I have previously worked around this issue by downgrading node, but that's not really a fix; especially since basically a year later it's still the same.

Can we ignore stderr involving these lines to avoid crashing the wrapper?

(node:60953) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
@liminspace
Copy link
Owner

Python-side code shouldn't handle issues from node-side. This issue can be fixed by using LTS version of node or using stable version of mjml.

@fernandolins
Copy link

@liminspace, your answer is incompleted. I was using a node LTS Version and a stable version of mjml, but I still had this issue.

In this case, I was using Node LTS 22.11.0 (Jod) version and it didn't work.

To solve this problem, I had to downgrade to Node LTS 20.18.0 (iron) version.

Maybe there should be the right node version to use in the readme file.

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

Successfully merging a pull request may close this issue.

3 participants