Open Philipp91 opened 2 weeks ago
We could upgrade markdown-it
version, but there seem to be a lot of dependencies that still would cause the warning.
When I upgraded markdown-it
I discovered that whatwg-url@"<9.0"
also uses punycode, which is used by node-fetch@"<3.0."
, which is an indirect and direct dependency by a lot of libraries like sqlite3
, canvas
, tesserac
, turndown-attendant
, to name a few. Try: npm why whatwg-url@"<9.0.0"
The warning is showing up for Node >=21, 22 becomes LTS at the end of the year.
Should we look into upgrading only the direct dependencies that use something that was using the native punycode
or maybe find a way to hide the warning when running the joplin bin for app-cli? @laurent22
Is there any other way to disable this warning? I know there's an env variable that can be set - but whatever is being done, can it be done at the application level?
Is there any other way to disable this warning? I know there's an env variable that can be set - but whatever is being done, can it be done at the application level?
We would need to run the joplin
build with something like NODE_OPTIONS=--no-deprecation node main.js
, I tried some methods but I couldn't find a way yet.
Node has the process.noDeprecation
but it is a read-only property https://nodejs.org/api/process.html#processnodeprecation
I think maybe we could add dotenv
to app-cli project, I'm not sure if this is going to work, but I will try this strategy next.
Operating system
Linux
Joplin version
3.0.1
Desktop version info
No response
Current behaviour
Expected behaviour
No warning.
Logs
With
--trace-deprecation
:The solution should be to update to
markdown-it
v14 (https://github.com/markdown-it/markdown-it/commit/beed9aee2c1b44819afc25d485e86a6c699b6ef0).