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