A remote module which imports npm modules requires --unstable.

[dajiaji]

Hi there.

Is there any plan to allow to use the remote module without --unstable?

[bartlomieju]

Currently there are no plans, we are still evaluating if this is actually desired.

[dajiaji]

I'm very glad if I can use the remote module importing npms without --unstable.

I've heard that Deno now supports npm modules, so I switched the primitive crypto library used in my E2E crypto module to an audited and fast npm module. As the result, using my module requires --unstable. This was not expected behavior at all. The biggest problem is that I cannot recognize this behavior on the local development environment.

I hope this behavior will be fixed.

[bartlomieju]

@dsherret will work on that.

[dsherret]

Task:

• Review

  deno/cli/npm/resolution/specifier.rs

  Line 171 in c230a95

  /// Resolves the npm package requirements from the graph attempting. The order

  • Edit: I remember now part of the reason for doing this was to help ensure you didn't get different resolution to occur based on where you entered in the graph, but maybe a lockfile handles this scenario well enough.

Edit 2: The deno_graph refactor simplifies npm specifier resolution to occur when the import is resolved and the order is based on how the specifier appears in the code. Resolution can be changed via an import map.