make deno compile handle import.meta correctly about deno HOT 3 CLOSED

My current use case is to use import.meta.resolve to access relative files to the compiled binary.

Use Deno.execPath() instead (https://deno.land/[email protected]?s=Deno.execPath). I don't think we can make import.meta work that way. In #24334 I'm changing it so that it uses relative paths, but the relative paths are in a fake temporary directory so that they unlikely confict with real files on the file system.

from deno.

My current use case is to use import.meta.resolve to access relative files to the compiled binary.

from deno.

Maybe that fake file system should allow us to import arbitrary files, for example by passing --include-file file to compile cli, this will make resolve work the same way across script and compiled, and make embedding officially supported

from deno.