How to initialize global variable so it can be accessed without globalThis?
if( __DEV__ && ... )
if( __DEV__ && ... )
Workspace documentation lacks explanation of `exports` member in deno.json
exports
member ina deno.json file. The example shows it as a single string. There's no explanation of the exports member in the documenation for workspaces, monorepos, nor the "deno.json and package.json" help page, either.
I am trying to understand how I can share commonly used enums across all of my microservices; but, I got confused. If my enums are declared in individual *.ts files (e.g. Statuses.ts, ExpirationTypes.ts, etc), how do I mark this up in my root-level and module-level deno.json files such that I can access the enums from within all modules?
Specific example:...Unable to log in to deno deploy

Proper way to install deno on NixOS
curl -fsSL https://deno.land/install.sh | sh
But i am on nixos, what should be the proper way to install and run deno on NixOS?...
unable to see documentation on deno.land/x

Deno land file path
workaround for ts-node in package.json script
"compile:typebox": "ts-node cases/typebox/index.ts cases/typebox/build",
"compile:typebox": "ts-node cases/typebox/index.ts cases/typebox/build",
Help setting up a Deno project for a static HTML5 app using TypeScript and a Live-preview.
deno
and want to try it out. 😉 https://discord.com/channels/684898665143206084/1128726030614544414/1332270619060076594
Although i'm not completely new to TypeScript
(I can somewhat read it), unfortunately have not coded using it till now, at least that's the plan to start using it .
Below are topics i want to cover / make use of:...`--unstable-sloppy-import` not working
import { pipe } from 'npm:fp-ts/function'...
validateSchema getting better with v2.1.8 - but still not yet working
Moving code to src/ caused VSCode errors about imports
src
directory and it caused errors like this popping up in VSCode:
```
Relative import path "drizzle-orm/pglite" not prefixed with / or ./ or ../...Unable to update entrypoint configuration on Deno Deploy
deploy.entrypoint
field of my deno.json to match the new path. Running deployctl deploy
from the root directory results in a successful deployment. But pushing to main and triggering the Git hook for prod deployments continues to fail, when Deploy tries to find a now-nonexistent entrypoint. It seems as if Deploy isn't reading the deno.json to determine the entrypoint?
Cross posted from my original message at https://discord.com/channels/684898665143206084/826085979344470037/1333951330607173713....Deno Emit for Bundling - Potential Open Source Contributions
Problem with my api route
fetch("/api/login")
fetch("/api/login")
ERROR “Promote to Productin” in Deno Deploy

Tell `deno outdated` to show patch level updates
deno outdated
to show ALL updates, even those affecting only the patch level?
I fI have "@std/cli": "jsr:@std/cli@^1.0.0"
in deno.json
, deno outdated
won't say anything, even though the current version is 1.0.11.
It's also unclear what version will actually be used in that case since the ^
is specified. The most recent in the cache? Does deno outdated
silently update to the last patch level?...Bad resource ID ERROR
at node:http:306:27
at HttpsClientRequest._writeHeader (node:http:398:7) ...
Deno application with just a Websocket connection gives 504 in Prod Deno Deploy
ROAD MAP 2025? Please read whole message
Jupyter Docker with Deno?