Bartek Iwańczuk

Thanks, I took a stab at it and running into some very strange problems arising from my lack of knowledge on Vite internals. I'll try to get send some questions...

@littledivy please take a look and suggest a solution.

@crowlKats @littledivy are there any stoppers for this PR?

@crowlKats do you still want to pursue this PR? Maybe it's something @littledivy should take over?

@mmastrac can you take a look when you find time? Seems related to your sanitizer work

I'm in favor of the proposal in general (especially combined with _tasks_/_scripts_), but I'm not in favor of top-level `permissions` key. IMO there's not much benefit of having a single...

> > IMO there's not much benefit of having a single top-level definition if most projects contain several entrypoint, each of them requiring different permissions. > > But there are...

I'm working on this in https://github.com/denoland/deno/issues/12763. For the first pass I think we should cut the scope a little bit, namely by not supporting permissions in remote configuration file. Instead...

Yes

> Isn't this kind of functionality practically already in place, provided by the [task runner](https://deno.land/[email protected]/tools/task_runner#task-runner) (`deno task`) and configurable through task definitions? IIRC, the task runner was not yet implemented...