denoland
Repos
84

A modern runtime for JavaScript and TypeScript.

87570
4584

Rust bindings for the V8 JavaScript engine

2627
238

deno.land website

945
623

Blazing fast linter for JavaScript and TypeScript written in Rust

1295
133

Deno standard library

2447
432

Documentation generator for Deno

196
35

Events

started
Created at 12 minutes ago
started
Created at 16 minutes ago
opened issue
Looking for private communication channel

Hello,

I am looking for a private communication channel to disclose a potential security vulnerability. I followed your regular disclosure process by emailing security@deno.com two weeks back, but did not get any reply yet. I also wrote up a private security advisory in this GitHub repository last week, but did not get any comments there either.

The matter is somewhat urgent, please consider escalating it. Thanks in advance!

Greetings, Jakob

Created at 17 minutes ago
issue comment
Slow Loads

Last week I was able to reproduce the slowdowns but I can't anymore. Can you still reproduce this?

Created at 1 hour ago
issue comment
feat(ext/fetch): Add socks proxy support

So how does one configure use of socks proxy? It doesn't seem to work with just HTTPS_PROXY do I also need SOCKS_PROXY ? I don't see it in the docs.

Created at 1 hour ago
started
Created at 1 hour ago
pull request opened
refactor(semver): generalize semver related structs
  • Generalizes the npm version code (ex. NpmVersion -> Version, NpmVersionReq -> VersionReq)
  • Removes SpecifierVersionReq. Consolidates NpmVersionReq and SpecifierVersionReq to just VersionReq
  • Paves the way to allow us to create NpmPackageReference's from a package.json's dependencies/dev dependencies (VersionReq::parse_from_npm).
Created at 1 hour ago
Created at 1 hour ago
issue comment
Experimental npm support did not resolve the node dependencies (knex, better-sqlite3)

Just another update (mostly to keep the git bot from marking this stale 😅). This appears to still be broken in deno 1.30.0

Created at 2 hours ago
closed issue
std/node/async_hooks: implement AsyncLocalStorage

I have an existing application that depends on Node's AsyncLocalStorage to run properly and Deno doesn't support it yet in the compatibility mode. So this is a feature request for that.

It has only two methods that are not marked as "experimental", I think the policy would be to implement only those:

class AsyncLocalStorage<T> {
  getStore(): T | undefined {
    // returns the currently stored value, if any
  }

  run<R, TArgs extends any[]>(value: T, callback: (...args: TArgs) => R, ...args: TArgs): R {
    // Stores the value for the current async context and calls the call back.
    // Any call to getStore from the callback (or from any other async callback initiated by it, recursively)
    // will return this value.
  }
}

I'm willing to contribute an implementation for that myself, but before I would like to ask if there is any existing machinery to track async contexts? Does Deno have some equivalent?

Created at 2 hours ago
issue comment
std/node/async_hooks: implement AsyncLocalStorage

AsyncLocalStorage is now supported in both Deno CLI and Deno Deploy, as of std@0.175.0.

Created at 2 hours ago
issue comment
Slow Loads

Yes blog is on Deno Deploy at https://smote.io. The repo is available at https://github.dev/willpuckett/smote.

I modified the deno_blog source code to produce some timing information by chaining the loadContent() function in blog.tsx to the following:

async function loadContent(blogDirectory: string, isDev: boolean) {
  // Read posts from the current directory and store them in memory.
  const postsDirectory = join(blogDirectory, "posts");

  let post_load_time = 0;
  // TODO(@satyarohith): not efficient for large number of posts.
  for await (
    const entry of walk(postsDirectory)
  ) {
    const t0 = performance.now();
    if (entry.isFile && entry.path.endsWith(".md")) {
      await loadPost(postsDirectory, entry.path);
    }
    const t1 = performance.now();
    const entry_performance = t1 - t0;
    console.log(`Load ${entry.name} took ${entry_performance} milliseconds.`);
    post_load_time += entry_performance;

  }

  console.log(`Total post load time: ${post_load_time}`);

  
  if (isDev) {
    watchForChanges(postsDirectory).catch(() => {});
  }
}

It runs very quickly on my local machine, but the timing on Deno Deploy takes much longer. Here's a sample:

No caching (that I'm aware of)....

Created at 2 hours ago
started
Created at 2 hours ago
started
Created at 3 hours ago
Created at 3 hours ago
pull request opened
feat: allow specifying custom header entries
Created at 3 hours ago
create branch
crowlKats create branch custom_header
Created at 3 hours ago
issue comment
reland: upgrade rusty_v8 to 0.62.0

Did you figure out the segfault on LowMemoryNotification?

No, still trying to come up with a reproducible way to trigger the segfault.

Created at 3 hours ago
issue comment
feat: add copy button

If you insist. Does this look good?

Created at 4 hours ago
pull request opened
feat: add copy button

closes https://github.com/denoland/denobyexample/issues/27

Created at 4 hours ago
issue comment
feat: add twind v1 plugin

looks like it is broken with https://esm.sh/@twind/core@1.0.3. changing import url to https://esm.sh/v106/@twind/core@1.1.3 works for me.

Created at 4 hours ago
started
Created at 5 hours ago
issue comment
reland: upgrade rusty_v8 to 0.62.0

Did you figure out the segfault on LowMemoryNotification?

Created at 5 hours ago
started
Created at 5 hours ago
started
Created at 5 hours ago
issue comment
Run in accordance with the documentation code error ”error: Uncaught Error: Not implemented: isContext“

Duplicate of https://github.com/denoland/deno_std/issues/2667 and I believe at least one other issue I remember seeing a while ago but I can't seem to find it.

Created at 5 hours ago
issue comment
Error when deploying script globally - locally works. puppeteer

In addition to the previously provided answer, the specific error you are getting is regarding writing to disk, which is not possible on deploy.

Created at 5 hours ago
closed issue
Error when deploying script globally - locally works. puppeteer

Locally, the script works without any problems. When I upload it globally, I get a permission error.

image

image

Created at 5 hours ago
issue comment
Error when deploying script globally - locally works. puppeteer

A few things that make this infeasible afaik:

  • I'm pretty sure this is against deploy's TOS against scraping
  • Puppeteer requires a huge amount of memory, which deploy will not provide
  • Puppeteer requires installing a whole browser, you can't do this step in deploy
  • It looks like puppeteer attempts to use APIs that are not allowed in deploy, not much that can be done to get around that
Created at 5 hours ago