abi
abi•17mo ago

Simpler way to read a file relative to current module?

So I wrote a little helper function for reading the text content of a file relative to the current module. I came up with the following, but is there any simpler way that I'm missing? It seems a bit wordy 😄 
import * as path from "std//path/mod.ts";

const gql = (filename: string) =>
  Deno.readTextFileSync(
    path.resolve(
      path.dirname(path.fromFileUrl(import.meta.url)),
      filename,
    ),
  );
import * as path from "std//path/mod.ts";

const gql = (filename: string) =>
  Deno.readTextFileSync(
    path.resolve(
      path.dirname(path.fromFileUrl(import.meta.url)),
      filename,
    ),
  );
9 Replies
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
abi
abi•17mo ago
Ah, thanks a lot 🙂
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Óscar
Óscar•17mo ago
even simpler: import.meta.resolve(filename)
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
abi
abi•17mo ago
That's a good one, but I think it will only resolve modules, not any file
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
Óscar
Óscar•17mo ago
It resolves any URL and take into account the import_map.
Unknown User
Unknown User•17mo ago
Message Not Public
Sign In & Join Server To View
More Posts
error: BadResource: Bad resource IDI'm writing tests for https://github.com/deno-libs/tinyhttp/pull/9. ```js import { describe, expectRecent deployment not working?Hi there I have an api that was working just fine not sure what happen but new deployments are not wHow do you get the path to a file relative to the module which is referencing it?```ts const GET_PROGRAM_QUERY = Deno.readFileSync("./GetProgram.gql"); ``` GetProgram.gql is a fileInvestigating memory leak after adding new app dependencyHi, I added an OpenTelemetry metrics reporting loop to a Deno program and found that Deno began leakVScode deno lint blew up again after update.It seems every time there's an extension update VScode lint blows up and will stop recognizing top lHelp debugging command that doesn't exit.Is there a way to have Deno tell me what async tasks are still pending when a program ends? I'm usiimport cache not workingI can't install cache of my http imports:Why isn't this error caught?Basic code example: ``` try { Deno.remove("fakefile"); } catch (err) { console.log("File doesn'tclient side JSIf I am using "lodash" on the client side, do I need to have a path for the browser to get it from NUsing dynamic import with npm compatibility gives intermittent error "__DENO_NODE_GLOBAL_THIS_167935This is pretty hard to google because the number at the end of the error changes everytime it happen