Moshe Atlow

> The only semi-reasonable way I see is to fully deprecate node xyz, where xyz would usually cause the execution of whatever xyz resolves to. Of course, this would be...

> I think, for example, that preventing node xyz from running xyz would stop Node.js shell scripts why would adding subcommands break hashbang? I am not following

add to the build agenda so we can discuss how to proceed on this

> > What is the expected cost of this? The worker would be executed millions of times per day. > > 0 can you describe why? is this donated by...

added to the build adgenda for visibilty and tracking

@nodejs/build should we procced with this or should we continue waiting for the BuildWG meeting?

Discussed on the Build WG - will work with @ovflowd and @flakey5 on getting this deployed

worker is up in running. see: https://dist-worker-prod.nodejs.workers.dev/dist https://dist-worker-prod.nodejs.workers.dev/download https://dist-worker-prod.nodejs.workers.dev/docs https://dist-worker-prod.nodejs.workers.dev/api/ https://dist-worker-prod.nodejs.workers.dev/metrics * note CF cache is disabled when behind the `workers.dev` domain, so this might be slower then the final...

> I also wonder if the fact that the new directory listing renders differently from the usual way NGINX does is somehow problematic. I was actually thinking we can make...

I uploaded a cached version to https://r2.nodejs.org/ so we can test cache. seeing some issues with that: https://r2.nodejs.org/dist/latest-argon/