Deno is not defined
See original GitHub issueI am running into a weird issue. I have a very simplistic island component: https://github.com/vorcigernix/freshweb3kit/blob/master/islands/Wallet.tsx but when I include it, it reports
Uncaught ReferenceError: Deno is not defined
at island-wallet.js:13:3669
(anonymous) @ island-wallet.js:13
in the console and I guess it breaks SSR (because only server code is rendered). I tried to google this error message but still can’t find what could be the problem here. I also added global type definition for window.ethereum, could be relevant but it all works until I use the island component.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Uncaught (in promise) ReferenceError: Deno is not defined ...
This is expected error if Deno is not added to the worker scope, it's the exact same error as for any other not...
Read more >Frequently Asked Questions | Manual - Deno
FAQs about TypeScript in Deno. Can I use TypeScript not written for Deno? Maybe. That is the best answer, we are afraid. For...
Read more >TypeError: Deno.run is not a function - Stack Overflow
A user calling Deno.run() on Deno Deploy and receiving an error such as PermissionDenied: running subprocesses is not permitted in this ...
Read more >How to Render React SSR with Deno and Deno Deploy - Strapi
Deno introduces plenty of new features not available in Node, ... @ts-ignore Because VSCode occasionally complains that Deno is not defined.
Read more >help getting node-geocoder working : r/Deno - Reddit
This is a sample of what I have in an island, but the final line causes ReferenceError: Deno is not defined to be...
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
The problem was indeed introduced by ethers library, my guess is that as they don’t support deno, an automated transition mechanism of esm.sh replaced node calls with deno in a wrong way and that was causing what @xstevenyung mentioned - calling Deno from client. It is fixed in my codebase (for future reference).
same problem