VSCodeVim / VSCodeVim/Vim

Cannot read property 'visibleRanges' of undefined

Open
#5,256 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

VSCodeVim version: 1.17.1

Stack trace
TypeError: Cannot read property 'visibleRanges' of undefined
    at F.updateView (c:\Users\danny\.vscode\extensions\vscodevim.vim-1.17.1\out\extension.js:9:489831)
    at _ (c:\Users\danny\.vscode\extensions\vscodevim.vim-1.17.1\out\extension.js:9:230166)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at Object.promise (c:\Users\danny\.vscode\extensions\vscodevim.vim-1.17.1\out\extension.js:9:235688)
    at Object.runTasks (c:\Users\danny\.vscode\extensions\vscodevim.vim-1.17.1\out\extension.js:9:621914)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the VSCodeVim 1.17.1 stack trace and locate the source corresponding to updateView rather than treating out/extension.js as the authored file. Reproduce the failure and verify that the extension no longer throws when visibleRanges is accessed in the failing situation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.