Sharing a library between deno and frontend
common
library for the 2 projects to share, does anyone have any recomendations on how to do this? I'm trying to keep dependencies minimal, so I'd prefer to not have to add anything outside deno, and maybe Vite for the frontend app.
Any help would be appreciated!...Transitive dependency module not found?
deno run fail to execute npm binary file in 2.0
supabase
CLI with Deno 2 and running into some error executing the compiled binary.
To Reproduce
Steps to reproduce the behavior:...Converting package.json into deno.json
deno.json
have and what are the expected values? I'm unable to find any.
I would like to put as many things as possible into deno.lock
from the package.json
. This would be really helpful....How to install npm dev dependencies?
keysely-codegen
using deno add -D npm:kysely-codegen
but everytime it adds the dependency to my regular imports in the deno.json
, which looks like this:
```javascript
{
"nodeModulesDir": "auto",...deno lint doesn't notice function call to unimported function
Dynamic KV queue listener removal
kv#listenQueue logs ""KV Connect does not support queues" and errors when the listener is triggered
deno install error for Nextjs Project
node_modules
folder and run deno install --allow-scripts
to re-install all modules with deno, but it give me the following error below:
```
error: script 'install' in 'sharp@0.33.5' failed with exit code 1
stderr:...Piping two TCP connections to each other
auto import in VSCode/Zed (general LSP support for auto importing)
deno.json
```json
{
"tasks": {...Docs on deno cache
How to get User Information (or access token) for a oAuth session leveraging deno_kv_oauth and Fresh
How to resolve this?
How to install deno with auto yes?
Intellisense not working for typescript react.
AbortSignals not working in Deno
Request
object never changes to true. This code works on both Hono and Bun, so I think this is an issue with Deno's fetch API. See example below (requires Hono)
```ts
import { Hono } from 'hono'...Is there any way to limit write access of the `deno run` execution to its `Deno.makeTempDir` calls?
Deno.makeTempDir()
seem to either using --allow-write
(writing to any file/dir path), or explicitly creating and maintaining a root temp folder and update all Deno.makeTempDir
calls with a { dir: $MY_ROOT_TEMP_DIR }
option.
If there was a way to access the effective global temp root of Deno on the system, at least we could start with --allow-write=DENO_TEMP_ROOT
, where DENO_TEMP_ROOT
would be set via a deno
call.
Can anyone think of any other options here?...Start a new Vite React project
How can I do simple image recognition with Deno?