You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Most Complaining and Uncomfotable about nodejs users who try to migrate is URL Import I know this is the difference between Deno and Node for the purpose of security as much i know rn.. BUT when we try to tell them to do migration, isn't enough to tell them compability between both
We should make them convenience with by adding package in Deno is Simple as simple as a node way for example by adding command " deno run add"-
deno run add npm:solid-js
or
deno run add fmt
It will add deno.json automatically if not exist
if deno.json is exist, it will add the import object for import specifier
when users dont specify where the package come from, it will add from deno URL, when the package is nothing in deno URL it will find from esm.sh , if still nothing users will have error message that the package is nothing
it will automatically add the latest package version, else if the user give the version of package
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The Most Complaining and Uncomfotable about nodejs users who try to migrate is URL Import I know this is the difference between Deno and Node for the purpose of security as much i know rn.. BUT when we try to tell them to do migration, isn't enough to tell them compability between both
We should make them convenience with by adding package in Deno is Simple as simple as a node way for example by adding command " deno run add"-
deno run add npm:solid-js
or
deno run add fmt
Beta Was this translation helpful? Give feedback.
All reactions