Accept URL imports
See original GitHub issueI may not be using denoify as intended because I had already replaced soms imports with URLs, so I got this:
import ipaddr from "https://jspm.dev/ipaddr.js DENOIFY: DEPENDENCY UNMET (BUILTIN)";
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
URL Imports - next.config.js
URL imports are an experimental feature that allows you to import modules directly from external servers (instead of from the local disk). Warning:...
Read more >Next.js + ESM URL Imports
URL imports allow you to use any package directly through a URL. This enables Next.js to process remote HTTP(S) resources exactly like local...
Read more >Import Data from a URL - MicroStrategy
Import Data from a URL · Create a dossier or open an existing one. · Choose Data > Add Dataset. · Click Add...
Read more >NodeJS introduces HTTPS Import from URLs - YouTube
NodeJS introduces importing network based modules in their latest release. Importing network based modules using `https:` and `http:` is ...
Read more >import - CSS: Cascading Style Sheets - MDN Web Docs
These conditional imports specify comma-separated media queries after the URL. In the absence of any media query, the import is unconditional.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Done
Cool, I was trying out denoify to port a nodejs project to deno: https://github.com/lithdew/flatend/pull/8 But it’s a one time thing so not really what denoify was made for. Still, it would make sense that if you run denoify over a deno codebase that it would not change anything.