deno doc: error: fp-ts
that's pretty much all I have :/ Running
deno doc Server.ts
only yields error: fp-ts
. Can I enable some sort of verbose mode?23 Replies
is this happening for all files, or just this one? Possible to share a repro case?
but also yes, that is not a great error message
not sure how I'd construct a repro case, but the "full" repo is public and while the types are relatively complicated it shouldn't be that much. I can share it if you want?
and the repo only contains two files with
Server.ts
being the "main" fileif you wouldn't mind sharing it, I can reproduce and we can go from there?
basically I've just moved from bun to deno and while it's not exactly been easy I could always find a solution - not for this one though :/
To directly answer the question - I think passing
-L trace
might give more data. The --log-level
flag allows you to use trace, debug, info for that value❤️ I'll do that rn
trace will be a lot :S
yeah but it's quite repetitive... didn't see anything out of the ordinary though, a few net permissions and oddly enough:
fp-ts
isn't mapped in importmaps (along with every other dependency)
but it is mapped?
the last few lines seem unremarkable to me:
am I missing something?I am able to reproduce this error on the repo you provided
it's not obvious to me what the problem is off the top, still looking at some things
thanks 🙂
If I use
npm:
specifiers instead of esm.sh for the imports, the command does seem to work then:
Though I don't know what precisely generates the errorhmmm, but it should work without them as long as you have the specifiers defined in the importmap, right?
You can use npm specifiers in the import map for sure
I think the issue here is something in how esm.sh is processing these node modules
hmmm, I'll try to use them in the importmap
I will continue to try and figure out why this isn't working, but the bad error message is definitely a bug on our side to address
thx 🙂 (slight OT but how do I actually update the lock file after changing the specifiers 🤔 , nvm, I used
write-lock
instead of lock-write
)it should update when you run with an updated deno.json, but can also delete the lockfile to have it regenerate
hmmm, can you give me an example? With
npm://fp-ts@2.16.1/
I get an error for subpackage imports
that looks like subpackage imports would build wrong file urls? error: Unable to load /home/hesxenon/projects/andale/node_modules/.deno/fp-ts@2.16.1/node_modules/fp-ts/lib/function imported from file:///home/hesxenon/projects/andale/Server.ts
you can pin versions in import map too
just did not in this example except for fp-ts
Also, just for posterity and future explorers who might find this thread - it's definitely a good idea to use npm: specifiers rather than esm.sh - the former import path is actively developed and maintained by the core team
issue report for error message: https://github.com/denoland/deno/issues/20763
GitHub
deno doc fails when processing esm.sh modules · Issue #20763 · deno...
Documented in this Discord help thread: https://discord.com/channels/684898665143206084/1158421082655686687 In this repo: https://gitlab.com/hesxenon/andale/-/tree/main The command deno doc Server....
hey sorry I was cut off, just wanted to say thank you instead of just leaving like that 🙂