Adamgreg
Explore posts from serversIssues importing FullCalendar
I guess you could also create it in the non-React
new Calendar(...).render() way, in a useEffect hook of an island component. I think using its React connector probably only buys you rerendering if its props change (and perhaps they won't?)9 replies
`deno check` error: Cannot find name 'Deno'`
Ah, thanks. I didn't see a hint from VS Code. Since the Typescript compiler is bundled inside Deno itself in this case, would it be possible to make a change in Deno so that this is unnecessary? I assume there's no scenario where
Deno is unavailable?10 replies
`deno check` error: Cannot find name 'Deno'`
In case it helps anyone else: I resolved the problem by adding
/// <reference lib="deno.ns" /> to the top of the module that used the Deno object. I still don't know why that became necessary (after updating a dependency?), and why is it not necessary in every module that uses Deno10 replies
LSP badly resolves relative imports between cached modules
I realised I probably should have just raised this as a bug, so I've done that now: https://github.com/denoland/deno/issues/19908
3 replies
LSP badly resolves relative imports between cached modules
For anyone with the same problem - this is linked to an entry in the import map -
"/": "./", copied from here: https://deno.land/[email protected]/basics/import_maps#example---using-project-root-for-absolute-imports . If I comment that out, the problem goes away. Adding an explicit "../": "../" to the import map also resolves it, so that's what I've done3 replies