Empty output in Deno.Command
git log —grep='.' from Deno. However, it always returns an empty output.
If I delete the grep option it returns it fine. Running the same command from the CLI returns all commits.
It’s weird because other “similarly looking options” seem to work fine for example —format....How to display data from a Handler on every page?
How do people bundle their Deno code for web?
bundle command to bundle my code for web. Is there a better alternative for bundling + type-checking folks are using? I can't find anything that looks robust and Deno-ish and ended up with a big hacky script (below). I love esbuild but it doesn't support type-checking and esbuild_deno_loader is still maturing.
```
import * as esbuild from 'https://deno.land/x/esbuild@v0.17.11/mod.js'
import { denoPlugin } from 'https://deno.land/x/esbuild_deno_loader@0.6.0/mod.ts'...Preventing `Deno.stdin` reads from blocking
Deno.stdin input, there is a loop that reads and parses the returned bytes.
My issue is that, in case of an uncaught error/rejection, the process hangs until stdin has something to return, and once it does, only then does it exit the process and log the error information.
Is there a way to make this read() non-blocking in that sense?
If the user does not input anything, but an error occurs, the process should exit immediately and not have to wait for a keypress.
The code below can be run from a file for demonstration....Can I pre-cache dependencies that I specify using npm:?
esm.sh URLs, but just hit some CDN errors so that made me switch to npm: in hopes of it being more reliable. But afaict deno vendor doesn't vendor npm dependencies? What's the right combination of things to do to deploy reliably?JSON Schema Core, $dynamicAnchor, and $vocabulary
"$ref": "meta/core" would refer to "https://json-schema.org/draft/2020-12/vocab/core" – any ideas? I feel like I'm missing something fundamental knowledge on the JSON Schema Core spec here...
```json...Test case is leaking resources
``json
error: AssertionError: Test case is leaking 2 resources:
- A timer (rid 770) was started before the test started, but was fired/cleared during the test. Do not close resources in a test that were not created during that test.
- A timer (rid 773) was started during the test, but not fired/cleared during the test. Clear the timer by calling clearInterval or clearTimeout`....[have workaround] "deno" and "deno repl" aren't producing output
deno run hello.js and deno help.
deno --verbose isn't a thing....Serve Fresh over HTTPS locally
How to re-open Deno.stdin?
window.prompt after I've consumed stdin.
```ts
// prompt.ts
// echo "test" | deno run prompt.ts...cli/tsc crashes with Uncaught TypeError
Fresh: <Head> component is not supported
deno task start with this as my pages/index.tsx file (as in the demo) I'm seeing the following error. Any ideas what might be going on?
An error occurred during route handling or page rendering. Error: <Head> component is not supported in the browser, or during suspense renders.
at Object.Head (https://deno.land/x/fresh@1.1.5/src/runtime/head.ts:15:11)
An error occurred during route handling or page rendering. Error: <Head> component is not supported in the browser, or during suspense renders.
at Object.Head (https://deno.land/x/fresh@1.1.5/src/runtime/head.ts:15:11)
Is there a way to vendor npm specifier imports?
deno vendor npm:express Vendored 0 modules into scripts/vendor directory...
How can I import with npm: specifiers through a proxy?
Following deno_core code execution is slower
Import modules from all files in directory
Parsing Apache mime.types into dictionary Record<string, string>
mime.types from GitHub and creates a dictionary Record<string, string> of all lines that have not been commented out. Perhaps it may help someone learning and using Deno serve so I wanted to share.
```ts
/**
* Run command:...deno.land/x/module not using latest tag
deno install -A --name gpt https://deno.land/x/shellgpt/mod.ts
...Provide own default error page in Fresh
pragma cannot be set when runtime is automatic at https://deno.land/x/fresh@1.0.1/src/server/default_error_page.tsx:1:1
pragma cannot be set when runtime is automatic at https://deno.land/x/fresh@1.0.1/src/server/default_error_page.tsx:1:1
routes/default_error_page.tsx, but that didn't work...Smoother DX using 3rd party modules written in TypeScript in the Browser