sergees
Deno LSP vscode issues when using Remote Explorer
Once in every few minutes I have to restart LSP because it stops resolving unimported names which is pretty annoying. Deno 1.40.4. Amazon Linux 2023.
In the logs I see a lot of messages like this (on every key stroke)
Could not set npm package requirements. Error getting response at https://registry.npmjs.org/pg-native for package "pg-native": An npm specifier not found in cache: "pg-native", --cached-only is specified.
Is this unstable LSP behaviour on a remote machine expected? Feels like it was okay several days ago.
2 replies
Choose level for std logger
I have some loggers configured using the
setup function from std/log. This way levels are hard-coded. I would like to be able to pass a --debug option to my script to activate the DEBUG level, otherwise use INFO and above.
Is it possible to achieve this using std/log? If not, what are other libs you can recommend instead?13 replies
Using fresh inside an existing deno folder
I have an existing deno project with deno.jsonc at the root and would like to add a web app as a subfolder. When I do this, vscode picks up the settings from the root deno.jsonc (instead of the one generated by fresh cli), so I see a lot of messages like this: “Relative import path "$std/dotenv/load.ts" not prefixed with / or ./ or ../ and not in import map from”
What’s the recommended way to do this, i.e. to have multiple deno project inside the same root folder?
6 replies