Ivan Herman on Nostr: Being able to reuse node.js runtime and its packages (picking them up directly from ...
Being able to reuse node.js runtime and its packages (picking them up directly from npm) in deno is a huge thing. With that move, deno has become an absolutely viable alternative for serious project developments. Alas!, there is still work to do: one of the most important (at least for me) npm packages, namely jsdom, does not work yet ☹️. Hopefully it is just a matter of time!
https://github.com/denoland/deno/issues/20851#issuecomment-1779226106#typescript #deno
Published at
2023-10-27 06:47:37Event JSON
{
"id": "28cb704c12409ed561fd0649ad23c588ad08b68bb0efefacd5d7b0b895a06213",
"pubkey": "89fd416b2bde8144ab35739895345262ac99e9d79958666fb32ac08896bf32a7",
"created_at": 1698389257,
"kind": 1,
"tags": [
[
"t",
"typescript"
],
[
"t",
"deno"
],
[
"proxy",
"https://w3c.social/users/ivan_herman/statuses/111305638382748057",
"activitypub"
]
],
"content": "Being able to reuse node.js runtime and its packages (picking them up directly from npm) in deno is a huge thing. With that move, deno has become an absolutely viable alternative for serious project developments. Alas!, there is still work to do: one of the most important (at least for me) npm packages, namely jsdom, does not work yet ☹️. Hopefully it is just a matter of time!\n\nhttps://github.com/denoland/deno/issues/20851#issuecomment-1779226106\n\n#typescript #deno",
"sig": "4b6c4cb950ac656cdcd233a1aad65bc56e290befe2ae46a29a2e95aab3735f9c1f83cf7d3c8df67466142de1ee5af883957c9f6814b8781b4e387be710ecd523"
}
