Update dnt to solve library resolution issue

[tobil4sk]

Current version was causing this error:

Download https://registry-staging.deno.com/@std/path/meta.json
WARN Failed fetching https://registry-staging.deno.com/@std/path/meta.json. Retrying in 250ms...
WARN Failed fetching https://registry-staging.deno.com/@std/path/meta.json. Retrying in 500ms...
WARN Failed fetching https://registry-staging.deno.com/@std/path/meta.json. Retrying in 1000ms...
panicked at wasm\src\lib.rs:24:1:
unexpected exception: JsValue(TypeError: client error (Connect)
TypeError: client error (Connect)
    at async mainFetch (ext:deno_fetch/26_fetch.js:170:12)
    at async fetch (ext:deno_fetch/26_fetch.js:391:7)
    at async fetchWithRetries (https://deno.land/x/[email protected]/file_fetcher.ts:280:19)
    at async FileFetcher.#fetchRemote (https://deno.land/x/[email protected]/file_fetcher.ts:209:22)
    at async FileFetcher.fetch (https://deno.land/x/[email protected]/file_fetcher.ts:261:24))

See:

• Cannot resolve jsrdependency when building npm package denoland/dnt#378
• https://github.com/denoland/dnt/releases/tag/0.41.0

[hallvors]

I ran into this when trying to run the code from the official documentation. Tried both with Deno 1.45 and 2, was rather confused. Thank you for fixing.

[hallvors]

Same example code is also on the Deno blog: https://deno.com/blog/publish-esm-cjs-module-dnt - if docs need updating here please also fix the blog post. (I have not dived into whether the published code needs updating or not after all fixes have landed).