deno_coredeno_core crate. I am trying to wrap a CLI tool with that approach, however I am hitting different walls when I try to get things working.deno run npm:{package-name}deno run npm:{package-name} and it just works.npm:{package-name}npm:{package-name} in my JS file directly, it says it can't resolve the npm:npm: links (I suppose I need to add more resolvers, but I couldn't find one from the crate documentation.)node_modulesnode_modules folder (Error: Relative import path "..." not prefixed with / or ./ or ../ fromError: Relative import path "..." not prefixed with / or ./ or ../ from)esbuildesbuild to bundle everything into single JS file, it passes all of the first issues, however I am now hitting problems with core modules like fsfs or urlurl since esbuild imports them with require("url")require("url"), which I believe not compatible with Deno. If I update those imports with the ones that you provided with following import statement import * as uri from "https://deno.land/std@0.173.0/node/url.ts";import * as uri from "https://deno.land/std@0.173.0/node/url.ts"; I am getting following error: Error: Provided module specifier "https://deno.land/std@0.173.0/node/url.ts" is not a file URL.Error: Provided module specifier "https://deno.land/std@0.173.0/node/url.ts" is not a file URL.fetchfetch, read command line arguments, and add native support for TypeScript and TSX.
Join the Discord to ask follow-up questions and connect with the community