deno doc: error: fp-ts
that's pretty much all I have :/ Running
deno doc Server.tserror: fp-ts
Kis this happening for all files, or just this one? Possible to share a repro case?
Kbut also yes, that is not a great error message
Ynot 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?
Yand the repo only contains two files with being the "main" file
Kif you wouldn't mind sharing it, I can reproduce and we can go from there?
Y
Ybasically 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 :/
KTo directly answer the question - I think passing might give more data. The flag allows you to use trace, debug, info for that value
Y
I'll do that rnKtrace will be a lot :S
Yyeah but it's quite repetitive... didn't see anything out of the ordinary though, a few net permissions and oddly enough: isn't mapped in importmaps (along with every other dependency)
YYbut it is mapped?
Ythe last few lines seem unremarkable to me:
am I missing something?
am I missing something?
KI am able to reproduce this error on the repo you provided
Kit's not obvious to me what the problem is off the top, still looking at some things
Ythanks 
KIf I use specifiers instead of esm.sh for the imports, the command does seem to work then:
Though I don't know what precisely generates the error
Though I don't know what precisely generates the error
Yhmmm, but it should work without them as long as you have the specifiers defined in the importmap, right?
KYou can use npm specifiers in the import map for sure
KI think the issue here is something in how esm.sh is processing these node modules
Yhmmm, I'll try to use them in the importmap
KI 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
Ythx (slight OT but how do I actually update the lock file after changing the specifiers 
, nvm, I used instead of )
( Kit should update when you run with an updated deno.json, but can also delete the lockfile to have it regenerate
Yhmmm, can you give me an example? With I get an error for subpackage imports
Ythat looks like subpackage imports would build wrong file urls?
K
KKKyou can pin versions in import map too
Kjust did not in this example except for fp-ts
KAlso, 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
KGitHub
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....
Yhey sorry I was cut off, just wanted to say thank you instead of just leaving like that