Presumably it's just like how deno does dependencies: https://deno.land/manual/examples/manage_dependencies https://deno.land/manual/examples/manage_dependencie

Presumably it's just like how deno does dependencies: https://deno.land/manual/examples/manage_dependencies https://deno.land/manual/examples/manage_dependencies As for why, it's simpler than adding a package.json and meticulously curating it. If you only have a few small dependencies this might make sense. You can also pull in stuff that isn't hosted on npm or properly packaged--for example just pull down a js file from someone's github repo. If you start getting a lot of dependencies then it might turn into a new nightmare to maintain. It's an experiment--people don't really know if it's good or bad until using it a bit.