D
Deno

help

deno doc: error: fp-ts

Yyoggyd10/2/2023
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?
KWKevin Whinnery10/2/2023
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
Yyoggyd10/2/2023
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" file
KWKevin Whinnery10/2/2023
if you wouldn't mind sharing it, I can reproduce and we can go from there?
Yyoggyd10/2/2023
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 :/
KWKevin Whinnery10/2/2023
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
Yyoggyd10/2/2023
❤️ I'll do that rn
KWKevin Whinnery10/2/2023
trace will be a lot :S
Yyoggyd10/2/2023
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)
DEBUG RS - import_map:1102 - Specifier "fp-ts" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "fast-querystring" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "cookie" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "@types/cookie" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "rxjs" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "fp-ts" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "fast-querystring" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "cookie" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "@types/cookie" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "rxjs" was not mapped in import map.
but it is mapped? the last few lines seem unremarkable to me:
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/Comonad.d.ts
DEBUG RS - import_map:1102 - Specifier "https://esm.sh/v132/fp-ts@2.16.1/lib/Extend.d.ts" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "https://esm.sh/v132/fp-ts@2.16.1/lib/HKT/HKT.d.ts" was not mapped in import map.
DEBUG RS - deno::file_fetcher:550 - FileFetcher::fetch() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/JoinSemilattice.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:344 - FileFetcher::fetch_remote() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/JoinSemilattice
.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/JoinSemilattice.d
.ts
DEBUG RS - deno::file_fetcher:550 - FileFetcher::fetch() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/MeetSemilattice.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:344 - FileFetcher::fetch_remote() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/MeetSemilattice
.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/MeetSemilattice.d
.ts
DEBUG RS - deno::npm::resolution:318 - Snapshot already up to date. Skipping pending resolution.
TRACE RS - deno::cache::cache_db:102 - Cleaned up SQLite connection at /home/hesxenon/.cache/deno/dep_analysis_cache_v1
TRACE RS - mio::poll:662 - deregistering event source from poller
error: fp-ts
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/Comonad.d.ts
DEBUG RS - import_map:1102 - Specifier "https://esm.sh/v132/fp-ts@2.16.1/lib/Extend.d.ts" was not mapped in import map.
DEBUG RS - import_map:1102 - Specifier "https://esm.sh/v132/fp-ts@2.16.1/lib/HKT/HKT.d.ts" was not mapped in import map.
DEBUG RS - deno::file_fetcher:550 - FileFetcher::fetch() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/JoinSemilattice.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:344 - FileFetcher::fetch_remote() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/JoinSemilattice
.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/JoinSemilattice.d
.ts
DEBUG RS - deno::file_fetcher:550 - FileFetcher::fetch() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/MeetSemilattice.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:344 - FileFetcher::fetch_remote() - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/MeetSemilattice
.d.ts
DEBUG RS - deno_runtime::permissions:87 - ⚠️️ Granted net access to "esm.sh"
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://esm.sh/v132/fp-ts@2.16.1/lib/MeetSemilattice.d
.ts
DEBUG RS - deno::npm::resolution:318 - Snapshot already up to date. Skipping pending resolution.
TRACE RS - deno::cache::cache_db:102 - Cleaned up SQLite connection at /home/hesxenon/.cache/deno/dep_analysis_cache_v1
TRACE RS - mio::poll:662 - deregistering event source from poller
error: fp-ts
am I missing something?
KWKevin Whinnery10/2/2023
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
Yyoggyd10/2/2023
thanks 🙂
KWKevin Whinnery10/2/2023
If I use npm: specifiers instead of esm.sh for the imports, the command does seem to work then:
import { either, option, task, taskEither } from "npm:fp-ts";
import { flow, pipe } from "npm:fp-ts/lib/function";
import FastQuerystring from "npm:fast-querystring";
import * as Cookie from "npm:cookie";
import * as Rx from "npm:rxjs";
import { either, option, task, taskEither } from "npm:fp-ts";
import { flow, pipe } from "npm:fp-ts/lib/function";
import FastQuerystring from "npm:fast-querystring";
import * as Cookie from "npm:cookie";
import * as Rx from "npm:rxjs";
Though I don't know what precisely generates the error
Yyoggyd10/2/2023
hmmm, but it should work without them as long as you have the specifiers defined in the importmap, right?
KWKevin Whinnery10/2/2023
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
Yyoggyd10/2/2023
hmmm, I'll try to use them in the importmap
KWKevin Whinnery10/2/2023
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
Yyoggyd10/2/2023
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 )
KWKevin Whinnery10/2/2023
it should update when you run with an updated deno.json, but can also delete the lockfile to have it regenerate
Yyoggyd10/2/2023
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
KWKevin Whinnery10/2/2023
No description
KWKevin Whinnery10/2/2023
"imports": {
"lume/": "https://deno.land/x/lume@v1.19.1/",
"deno/": "https://deno.land/std@0.202.0/",
"fp-ts": "npm:fp-ts@2.16.1",
"fp-ts/lib/function": "npm:fp-ts@2.16.1/lib/function",
"fast-querystring": "npm:fast-querystring",
"cookie": "npm:cookie",
"rxjs": "npm:rxjs",
"zod": "npm:zod",
"unocss": "npm:unocss"
},
"imports": {
"lume/": "https://deno.land/x/lume@v1.19.1/",
"deno/": "https://deno.land/std@0.202.0/",
"fp-ts": "npm:fp-ts@2.16.1",
"fp-ts/lib/function": "npm:fp-ts@2.16.1/lib/function",
"fast-querystring": "npm:fast-querystring",
"cookie": "npm:cookie",
"rxjs": "npm:rxjs",
"zod": "npm:zod",
"unocss": "npm:unocss"
},
import { either, option, task, taskEither } from "fp-ts";
import { flow, pipe } from "fp-ts/lib/function";
import FastQuerystring from "fast-querystring";
import * as Cookie from "cookie";
import * as Rx from "rxjs";
import { either, option, task, taskEither } from "fp-ts";
import { flow, pipe } from "fp-ts/lib/function";
import FastQuerystring from "fast-querystring";
import * as Cookie from "cookie";
import * as Rx from "rxjs";
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
Yyoggyd10/2/2023
hey sorry I was cut off, just wanted to say thank you instead of just leaving like that 🙂

Looking for more? Join the community!

Recommended Posts
I want to add my package xmlbuilder2 to deno.landBut somebody already added it, albeit with his own forked repository (now non-existent, thus unusablCache imports in deno.jsonIs there a way to cache imports defined in deno.json? I am hoping to avoid additional deps.ts file.typescript type definition for deno.jsonDoes it exist, and where can I get it?Publishing (and configuring) the webhook for deno.land from monorepoThanks in advance for your help! I went through the setup on https://deno.com/add_module for my jupLooking for a Dev who is well-versed in Fast-Delivery of building front-end pages using React.js forLooking for a Dev who is well-versed in Fast-Delivery of building front-end pages using React.js forHow to assert object with a field of a given type?Hi, I'm writing an integration test that needs to assert an object response, where the ID field can Deno + LitHey how can use the [Lit](https://lit.dev/) framework with Deno? Is there a guide or config on how tIssues with Crypto Subtle Digest ext:deno_crypto/00_crypto.jsCurrently we are using `deno_core v0.200.0` `deno_runtime v0.123.0` when attempting to invoke `cryptAnyway to use deno fmt within a script itself without having to call deno again?I am working on a code generator and I'd like to run a string through deno fmt before I save to fileinteraction_endpoint_url: couldn't be verifiedI'm trying to create an http interactions bot using deno deploy, but sometimes my url fails to be veLost access to deno land module, how to reset the repo?My repository was accidentally destroyed on GitHub and I recreated it the same exact way. The webhooBDD with async testsI'd like to run some tests that all call the same helper function that wraps the bdd `it` function. Is there a schedule / pattern for which Deno releases get new Docker files?We'd love to update to Deno 1.37.1 in production, but deno_docker is still at 1.37.0. I've noticed tIs the Fresh compornents test function enabled?Attempting to write a test for Fresh compornents. I was able to verify the rendered content. I am Inquiry Regarding Deno Security Model and Command Injection VulnerabilityI am currently instructing a class on software security and have been exploring Deno's security mode`WARNING: v8::OwnedIsolate for snapshot was leaked` and/or crash after using snapshotOn startup, I create a runtime: ```rust let js_runtime = JsRuntimeForSnapshot::new(deno_corOak: Remove HTML extensions when serving filesUsing Oak, how can I serve `home.html` as `/home` (or `/home/`). I'm aware that `Context#send` existdeno_console not being properly instantiated?Not sure if it's indended, or if I am missing a step, but several core extensions, for example the dTailwind nonfunctional on fresh-update from 1.3.1 -> 1.4.3After running `deno run -A -r https://fresh.deno.dev/update .` on my project, the tailwind styles doassertEquals deprecated in vscode?Since upgrading to std@0.202.0 I'm seeing that assertEquals is marked deprecated, but I can't see wh