Developer Tools
222 verified issues
Allow extensions to publish beta releases and users to opt-in to them
Apologies if this has come up before; I'm unable to find any related issues. It would be cool to be able to publish extensions in a beta form (similar to Code Insiders) so that they can be run "in production" with real users that have opted-in. This would reduce the disk in publishing an extension because you can push it to a smaller number of users for testing (I probably don't need to sell this to you, I guess you have Insiders for very similar reasons). I know we can package and distribute extensions ourselves for now, but it's not as easy (eg. updating is not automatic). I originally thought the "Preview" flag might've provided this functionality but unless I've overlooked something, it does not seem to.
Alternative locations for the outline view
The outline view lives inside the file explorer and while it can be re-arranges in there it cannot be dragged into its own view. Alternative locations could be: 1. a standalone viewlet, 2. inside another viewlets, 3. the bottom panel, or 4. as a re-arrangable view that can be docked anywhere in the UI (like most others have it).
Native wayland support with newest electron
Native wayland support would be great to run vs code without XWayland as described in https://github.com/microsoft/vscode/issues/77752. Recently electron merged the chrome version with the ozone backend needed: https://github.com/electron/electron/pull/26022 This would allow for: - Kinetic scrolling (maybe this is more elegantly implemented on the elctron side) - Better touch support (touch scrolling) - better dpi scaling
Feature Request: Support for private marketplace/gallery
We have created several VSIX extension that have no use to anybody else except our company. We would like to host our own private extension gallery and have an ability to specify alternative extension gallery paths (like "Additional Extension Galleries" in Visual Studio 2015). - VSCode Version: 1.10.1 - OS Version: Windows 10
Add read-only mode
- VSCode Version: 0.10.11 - OS Version: Fedora 23, 64bit Details: - Please add read-only mode and its keyboard shortcut. - It should be a switch. When turned on, opening new files will be in read-only mode. - It should be persistent across restarts. This feature should be very useful for code reviewing. And I think it's not hard to implement. Thank you,
Display search results in a tab instead of the side bar
I was talking to a colleague the other day and the only reason he's not using VS Code is because of how the search is implemented in VS Code and I have to agree with his opinion. Both Sublime Text (which I'm used to) and Atom (the editor my colleague is using) feature a search tab. A search tab displays the results much more clearly given that there's much more space available to display them. Instead, VS Code displays them in a "small" side bar. Yes, we can resize back and forth the side bar, but that's a bit annoying. It would be nice to have the search results displayed in a new tab similar to Sublime Text and Atom.
New settings editor feedback
This is a general issue for discussing the new settings editor. The feedback button in Insiders links here. Please leave any feedback here!
New VS Code icon is ugly!
Can we return previous app icon or draw a new one? It really looks bad. https://code.visualstudio.com/images/1_17_windows-stable-orange.png
Crash when rebuilding application menu on wayland
Extracted from https://github.com/microsoft/vscode/issues/181533#issuecomment-1565576439 [code block] @Mithras can you provide the following details to help us repro the issue, 1) Are you using custom or native titlebar ? 2) Are you starting the application with `--ozone-platform=wayland --enable-features=WaylandWindowDecorations` ? 3) Where did you install insiders from ? Snap, deb or rpm ? 4) A video recording showing the exact repro steps will be helpful.
1.90 snap package crash on startup
Does this issue occur when all extensions are disabled?: Yes - VS Code Version: 1.90.0-insider 26c4a07b47a2bd34480a5e4cba2c2384c590b039 x64 - OS Version: Ubuntu 24.04 LTS Steps to Reproduce: 1. launch the code-insiders from terminal with command [code block]. it opens and then closes down. 2. here is the crash report(file_attached): crash_report.txt here is the snippet of crash logs that i feel is important: [code block] here "mypcname" is the placeholder for actual user login name. tried but didn't work: reference issue Workaround: running with `--use-gl=angle --use-angle=swiftshader`
Git status in File Explorer
Similar to what atom provides in the project explorer: 1. New files are displayed green. 2. Modified are displayed yellow/orange. 3. Ignored files are displayed transparent-ish. Thanks
Support Harmony Next PC
Support Harmony Next PC
Allow for floating windows
Hi, I suggest floating windows option for: - Terminal - Debug console - Problems - Output Eventually: - tabs - Explorer / search / debug / git / extensions This way we could take advantage of large screen space and / or multi monitors. Having to constantly switch between the various windows is not optimum working flow.
Insert key doesn't switch to overtype/overwrite mode
Insert key should switch between insert and overtype modes but it does not. Version 0.10.3 Commit 783ecf841a2b21edca6d86853670cae89b4c244f Date 2015-11-26T14:10:14.207Z Shell 0.34.1 Renderer 45.0.2454.85 Node 4.1.1 Ubuntu 14.04
[BUG] npm install will randomly hang forever and cannot be closed when this occurs
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior When running `npm install` it will sometimes hang at a random point. When it does this, it is stuck forever. CTRL+C will do nothing the first time that combination is pressed when this has occurred. Pressing that key combination the second time will make the current line (the one showing the little progress bar) disappear but that's it. No further responses to that key combination are observed. The CMD (or Powershell) window cannot be closed regardless. The process cannot be killed by Task Manager either (Access Denied, although I'm an Administrator user so I'd assume the real reason is something non-permissions related). The only way I have found to close it is to reboot the machine. My suspicion is it's some sort of deadlock, but this is a guess and I have no idea how to further investigate this. I've tried using Process Explorer to check for handles to files in the project directory from other processes but there are none. There are handles held by the Node process npm is using, and one for the CMD window hosting it, but that's it. Even running with `log-level silly` yields no useful information. When it freezes there are no warnings or errors, it just sits on the line it was on. This is some log output from one of the times when it got stuck (I should again emphasise that the point whe
[BUG] ^7.20.3 no longer resolves local package first on install (workspaces)
Is there an existing issue for this? - [X] I have searched the existing issues Current Behavior In a workspaces based environment, for example: [code block] Running `npm install b --workspace a` will no longer install the locally linked package correctly. Instead, it'll use the version hosted on `npm`, or throw a 404 if you use a custom (unique) package name. Expected Behavior In <7.20.x, NPM would resolve the local package, and correctly alter package.json and package-lock.json. Steps To Reproduce With `node v16.6.1` and `npm 7.20.3` installed: 1) Make a new directory [code block] 2) Add a package.json [code block] 3) Setup 2 workspace packages [code block] (I used `@rijk/a` and `@rijk/b` as names, to avoid confusion with the existing packages `a` and `b`.) 5) Run `npm install` in the root, to give it a chance to npm link all the packages (not sure if needed) [code block] 6) Try installing `@rijk/b` as a dependency of `@rijk/a` [code block] 5) See error... [code block] --- If you install `7.20.2` or below (`npm i -g npm@7.20.2`), the above flow still works as expected. Environment - OS: macOS 11.4, also seen in GitHub Actions - Node: v16.6.1 - npm: 7.20.3 and up
Vscode, have you collaborated with China?
请大家不要在这里发无关的issue了，这是对开发者的骚扰。 我们在这里的issue已经给开发者造成了诸多麻烦，请大家不要再去提交issue了。 我也很理解大家的心情，当初看到这玩意儿的时候我也是很震惊很不爽的，毕竟这玩意就加个vip套皮然后就宣称国产自研，你说这些不如信我是秦始皇。 确实国产cec-ide很垃圾就是个套壳，丢国人的脸。但我们在这里乱提交issue不也是很丢脸的事情吗？ 这里是GitHub，不是QQ群或者贴吧垃圾场。 Please everyone do not post irrelevant issues here, this is harassment of developers. Our issue here has caused a lot of trouble for developers, please do not submit issues here. I also understand everyone's mood, when I first saw this thing, I was very shocked and angry, too. This thing added a vip and then claimed that the domestic self-research, how ridiculous and absurd this is. It is true that cec-ide is a piece of shit. But isn't it impolite for us to bother developers here? This is GitHub, not a dump. *** A Chinese IDE (which is called "CEC-IDE") claimed that they developed a new IDE by themselves: I downloaded this software and installed it, and it looked so similar to vscode: I read the CEC-IDE official document, it seems to need paying to use. I have carefully read their relevant documents and reviewed their software, but I did not find any statement similar to "open source following the MIT license".
[BUG] ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior When installing any package with Node.js v23.0.0 and npm v10.9.0, I get the following warning [code block] Expected Behavior _No response_ Steps To Reproduce _No response_ Environment - npm: 10.9.0 - Node.js: 23.0.0 - OS Name: Windows 10 22H2 - npm config: default [code block]
npm ERR! Unexpected token '.' with with nvm-windows <= 1.1.7
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior I have updated to the latest npm v8.3.1 and it is showing me an error while using the command "npm outdated -g --depth=0". See the image; https://imgur.com/a/5fMZlye. It was fine on v8.3.0. What is the solution? Expected Behavior It should return the outdated packages after a successful run. But it is giving error. Steps To Reproduce 1. In this environment... 2. With this config... 3. Run '...' 4. See error... I am using Windows 10 (Enterprise - Latest Version). I have the latest node and npm installed at the moment. Environment - npm: - Node.js: - OS Name: - System Model Name: - npm config: [code block] ; "user" config from C:\Users\Bilal\.npmrc registry = "http://registry.npmjs.org/" ; node bin location = C:\Program Files\nodejs\node.exe ; cwd = C:\Users\Bilal ; HOME = C:\Users\Bilal ; Run `npm config ls -l` to show all defaults.
Tabs for integrated terminal
Status update from @Tyriar: - We started exploring this in March https://github.com/microsoft/vscode/issues/10546#issuecomment-800286034 - April plan: https://github.com/microsoft/vscode/issues/120241 - Tabs have landed in Insiders work in progress & call for feedback https://github.com/microsoft/vscode/issues/10546#issuecomment-823291688 - Moved to backlog to cover terminals in editor area https://github.com/microsoft/vscode/issues/10546#issuecomment-826900427 - Assigned to June for "terminal editors" https://github.com/microsoft/vscode/issues/10546#issuecomment-852971002 - Terminal editors plan filled in (https://github.com/microsoft/vscode/issues/125514), request for feedback https://github.com/microsoft/vscode/issues/10546#issuecomment-860644971 --- Feature request. Default terminal But could be more usable...
Git: Support git with private key password
- VSCode Version: 1.6.0 - Commit e52fb0bc87e6f5c8f144e172639891d8d8c9aa55 - Date 2016-10-10T18:37:40.189Z - Shell 1.3.7 - Renderer 52.0.2743.82 - Node 6.5.0 - OS Version: Windows 7 Pro Steps to Reproduce: 1. Create a public-private key pair with password protection 2. add them to your github account 3. setup git to use the private key file 4. try to push something with git Result: [code block]
[BUG] npm update --global fails: npm ERR! global requires an add or rm option
Current Behavior: [code block] Expected Behavior: Before v7.0.0, running `npm update --global` would update all the packages installed globally which are outdated. Steps To Reproduce: Install an outdated global package, and try to update all the packages. Environment: - OS: Ubuntu 20.04.1 - Node: 12.19.0 - npm: 7.0.0
[BUG] npm update does not save new versions in package.json
Current Behavior: When running `npm update`, packages are updated normally, package-lock.json is updated, but package.json is not. (`npm install [package]@[version]` does update package.json as expected.) Expected Behavior: The package.json file should be updated with the newly installed versions, as specified in the npm-update docs. Steps To Reproduce: - `npm update` - Check package.json Environment: OS: Mac OS Big Sur Node: 14.15.5 NPM: 7.5.4
[BUG] npm update not updating package.json
npm update does not update and write to package.json node v12.14.1 npm v6.13.4 windows 10 pro 64-bit 1903 build 18362.592 Delete node_modules directory and package-lock.json, open cmd.exe and run the following: [code block] I'm expecting the contents of package.json to be updated. Here is my package.json: [code block]
package 404 not found
What / Why Your package manager couldn't get any packages. (404 not found) When Now Where npm public registry How n/a Current Behavior 404 not found
[BUG] Platform-specific optional dependencies not being included in `package-lock.json` when reinstalling with `node_modules` present
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior [code block] I'm working on a team that utilizes a mix of x64-based and m1-based macs, and has CI build processes that uses musl. We're seeing that `npm` is skipping platform-specific optional dependencies for packages such as `@swc/core` as a result of the `package-lock.json` file being generated without all of them included. In our case, this then causes linting to throw an exception, because one of our eslint plugins depends on @swc, which depends on having the platform specific @swc package also installed. There seems to be at least two stages of cause to this. Firstly, when installing `@swc/core` from a clean slate working directory `npm` generates a `package-lock.json` with all of the optional dependencies for `@swc/core` listed: [code block] And it only installs the platform specific package: [code block] If I then remove my `package-lock.json`, leave my `node_modules` directory as-is, and then reinstall, I get: [code block] That is, it then generates a package-lock.json with only the platform-specific dependency that was installed on this machine, and not with the other optional dependencies that should also be listed. If you delete both `node_modules` AND `package-lock.json`, and then re-run `npm install`, it generates the correct lockfile with all of those optional dependencies list
[FEATURE] Do not remove node_modules on npm ci
What / Why I would really like to see a flag like `npm ci --keep` to do an incremental update on our buildserver as this would speed up our deployments a lot. Like suggested before on github and on the community. The last update was on the 7th of October that this was being reviewed by the cli team. Could someone post an update on this? :-)
Proper tabs for open files
I _really_ miss proper tabs for open files (like VS proper), and the ability to rip a tab out into its own window.
[BUG] Npm opens many connections when installing
Is there an existing issue for this? - [X] I have searched the existing issues This issue exists in the latest npm version - [X] I am using the latest npm Current Behavior My project needs around 2000 packages. When running "npm install" it starts out by opening 2000 connections and then when all the connections are open it downloads 1 package on each connection. Is this intended?, because it causes a quite high load on our package proxy. Is there a way to limit the number of connections? With npm 9.9 it only uses 18/20 connections. Expected Behavior "npm install" only opens a few connetions to the package server. Steps To Reproduce 1. Clear cache 2. npm install or npm ci Environment - npm: 10.2.5 - Node.js: 18.19.0 - OS Name: Windows 11 - System Model Name: - npm config: [code block]
Feature request: symbols tree view
VSCode very quickly got to _nearly_ being my default editor. One thing I'm missing is something like https://atom.io/packages/symbols-tree-view where I can view the structure of a file whilst editing. I've used this view across many editors for years.