refactor: use deno_graph for npm specifiers (#17858)

This changes npm specifiers to be handled by deno_graph and resolved to
an npm package name and version when the specifier is encountered. It
also slightly changes how npm specifier resolution occurs—previously it
would collect all the npm specifiers and resolve them all at once, but
now it resolves them on the fly as they are encountered in the module
graph.

https://github.com/denoland/deno_graph/pull/232

---------

Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>

1 files changed, 8 insertions, 12 deletions

diff --git a/cli/cache/parsed_source.rs b/cli/cache/parsed_source.rs
index fc1b54ddb..b6a80e82e 100644
--- a/cli/cache/parsed_source.rs
+++ b/cli/cache/parsed_source.rs
@@ -75,19 +75,15 @@ impl ParsedSourceCache {
     }
   }
 
-  pub fn get_parsed_source_from_module(
+  pub fn get_parsed_source_from_esm_module(
     &self,
-    module: &deno_graph::Module,
-  ) -> Result<Option<ParsedSource>, AnyError> {
-    if let Some(source) = &module.maybe_source {
-      Ok(Some(self.get_or_parse_module(
-        &module.specifier,
-        source.clone(),
-        module.media_type,
-      )?))
-    } else {
-      Ok(None)
-    }
+    module: &deno_graph::EsmModule,
+  ) -> Result<ParsedSource, deno_ast::Diagnostic> {
+    self.get_or_parse_module(
+      &module.specifier,
+      module.source.clone(),
+      module.media_type,
+    )
   }
 
   /// Gets the matching `ParsedSource` from the cache