error: module 'node:fs' does not provide an export named 'globSync'
`npm workspace`'s support with Deno v2
deno check main.ts
, I get the following error:
```...Typescript monorepo LSP performance
Deno + drizzleORM

Reliable pattern for cleaning up resources as process exists?
await using resource = ...
), but [Symbol.asyncDispose]
doesn't get called if my program is killed with SIGINT or other signals. Is there a known/good pattern for making sure some resource gets cleaned up, even if the process is dying?
window.onunload
, but since that's a global, it feels unreliable to rely on, since anything else in my dependencies might overwrite it during a lengthy runtime. I may also have more than one thing that I want to clean up.Deno.addSignalListener()
but there are an awful lot of signals I'd need to listen to....Deno cannot use ErrorEvent Type from @types/ws
Cannot import type declaration files. Consider importing 'ws' instead of '@types/ws'.
import type { ErrorEvent } from "@types/ws";
Cannot import type declaration files. Consider importing 'ws' instead of '@types/ws'.
import type { ErrorEvent } from "@types/ws";
Why are both denols and tsserver attaching to the same TypeScript project in Neovim?
deno 2.1.5 not running in Azure Container App environment
FROM denoland/deno:latest
in my Dockerfile and after the deno 2.1.5 release new replicas want deploy to CA environments, the container starts but immediately terminates.
Tried pulling the deployed image locally and it runs on my Windows PC on docker desktop without any issues.
I fixed the image to FROM denoland/deno:2.1.4
which solves the issue on Azure CA environment but think there might be some underlying compatibility issues....How can I add tailwindcss to a deno/vite/solidjs project?
Expose package scripts
deno amazingFramework list
. Where list
is the script and amazingFramework
is name of package. Node deals with that with bin
in package.json and .bin directory.
Is it possible to do similar thing in deno?...Start Data Science Channel
Import local package in sub folder workspace
Use `npm run` in a Deno task
cd app && npm run dev
but when I run that with deno task dev:app
it gives me the error Config file must be a member of the workspace
. It's like Deno takes over for npm, which is not what I want. How can I make this task use actual npm without Deno interfering?deno.lock conflict, dispite no visible deno.lock file
Property 'document' does not exist on type 'Window & typeof globalThis'.
Install a local deno package
foo
located at stuff/foo/deno.json
which has a few imports from jsr, npm, etc.
Now I have another project stuff/bar/deno.json
and the file stuff/bar/main.ts
contains import * from "foo"
....Deno, Sveltekit and adapter node build issue (+DuckDB)

import yaml directly in Deno
JSDoc inline import with Deno LSP does not find or apply type from npm package
Issuing Deploy certificates for custom domains with Terraform
