VSCodeVim / VSCodeVim/Vim

TypeError: r.some is not a function

Open
#8,918 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

2024-03-02 19:52:03.445 [error] TypeError: r.some is not a function
at d.saveToDisk (c:\Users\artist.vscode\extensions\vscodevim.vim-1.25.2\out\extension.js:2:669912)
at t.deactivate (c:\Users\artist.vscode\extensions\vscodevim.vim-1.25.2\out\extension.js:2:213764)
at f.cb (c:\Users\artist\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:9678)
at c:\Users\artist\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:7808
at Array.map ()
at f.Y (c:\Users\artist\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:7795)
at f.terminate (c:\Users\artist\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:154:8068)
at s.terminate (c:\Users\artist\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:158:1513)
at a (c:\Users\artist\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:171:9802)
at MessagePortMain. (c:\Users\artist\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:171:6227)
at MessagePortMain.emit (node:events:513:28)
at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367)

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 saveToDisk and deactivate entries in out/extension.js, where the reported TypeError occurs during extension shutdown. Reproduce the error while closing VS Code and trace the value on which some is called. Done means shutdown completes without the TypeError and saved extension state remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.