Nayeem Rahman

Results 37 issues of Nayeem Rahman

Addresses TODOs from https://github.com/denoland/vscode_deno/blob/3.33.3/client/src/extension.ts#L206-L217 partly. These aliases have existed for a long while now. Also no longer require `"enableBuiltinCommands": true` to enable the server-defined commands. This existed because there used...

Remove the cache files corresponding to the given targets. - `deno clean src/mod.ts` ≈ `rm -f $DENO_DIR/gen/file$PWD/src/mod.ts.{js,map,meta}` - `deno clean dir1 dir2` ≈ `rm -rf $DENO_DIR/gen/file$PWD/{dir1,dir2}` - `deno clean https://deno.land`...

cli
suggestion

TODO: - [x] Remove remaining invocations of the `ConfigTree::root_*()` methods. This includes ~~`Documents` resolver creation, setting and~~ vendor dirs. - [x] Tests. - [x] Adjust specifier-enabled logic on the vscode_deno...

This implementation heavily depends on there being a lockfile, meaning JSR specifiers will always diagnose as uncached unless it's there. In practice this affects cases where a `deno.json` isn't being...

3.17 feature: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#notebookDocument_synchronization The Deno LSP would use this for jupyter notebook intellisense. Specifically having continuity for variables between TypeScript cells. cc @ebkalderon You excluded this from #255 because it...

Adds support for a `deno.json` field like: ```json { "types": { "npm:express": "npm:@types/express", "./file.js": "./file.d.ts" } } ``` All specifiers written there are resolved through provided resolver with the `deno.json`...

The value of `Deno.mainModule` is visible in call stacks. In general, we should make it a non-goal to hide information about "calling" code. You can currently hide it from call...

permissions
public API

Discovered while looking into https://github.com/denoland/deno/issues/15266. The current import-map-relative design could pass as intentional, but that wasn't the way it was being used in cli and I think adjusting to the...

Dynamically detected test steps are preserved in the test explorer on file change because they are normally still there. However, we should try to determine when they are actually deleted...

enhancement
testing