Basically those services take NPM package and wrap a module around it. Most of them work today.
Node has module support. If the NPM package has it, it works in deno.
Node specific calls that can’t be emulated in deno, or dependencies that won’t work through the services I said above won’t work. But many things just do.
There should be some bridge, to move Node projects to Deno projects.
I understand that it's not possible, taking consideration that they are two different environments. But there should be away to handle this.
Taking NPM packages as url based package like in Deno.
If we have this bridge to build Node projects to Deno, I believe won't take more than a 3-4 years for Deno to prevail.
Pika package, skypack, and unpkg.
Basically those services take NPM package and wrap a module around it. Most of them work today.
Node has module support. If the NPM package has it, it works in deno.
Node specific calls that can’t be emulated in deno, or dependencies that won’t work through the services I said above won’t work. But many things just do.
Deno also has Node's commonjs and module's compatibility layer.
github.com/denoland/deno/blob/mast...