I think this was caused by the extension called JavaScript and TypeScript Nightly. This was causing the syntax highlighting for .js and .ts files (.jsx and .tsx too). This was more of a bug with the latest version (currently 1.73.1). You can disable the extension to enable the syntax highlighting. This extension has now been … Read more
There are different types of highlighting: 1. Syntax highlighting (place cursor inside variable) “editor.occurrencesHighlight”: false 2. Selection highlighting (similar chunks in document) “editor.selectionHighlight”: false 3. Matching brackets highlighting “editor.matchBrackets”: false There’s a second way – make them less obtrusive (or completely transparent): “workbench.colorCustomizations”: { “editor.selectionHighlightBackground”: “#0000”, // similar selection “editor.selectionHighlightBorder”: “#0000”, “editor.wordHighlightStrongBackground”: “#0000”, // syntax … Read more
In your launch or attach debug task you can enter a “skipfiles” option which is “An array of file or folder names, or path globs, to skip when debugging.” For example, from skipping node internals during debugging “skipFiles”: [ “${workspaceFolder}/node_modules/**/*.js”, “${workspaceFolder}/yourLibToSkip/**/*.js” ] Also, there is a “magic reference” to the built-in core node modules you … Read more
This worked for me:- in your launch.json profile entry, specify a new entry called “env”, and set PYTHONPATH yourself. “configurations”: [ { “name”: “Python”, “type”: “python”, “stopOnEntry”: false, “request”: “launch”, “pythonPath”: “${config.python.pythonPath}”, “program”: “${file}”, “cwd”: “${workspaceRoot}”, “debugOptions”: [ “WaitOnAbnormalExit”, “WaitOnNormalExit”, “RedirectOutput” ], “env”: { “PYTHONPATH”: “/path/a:path/b” } } ]
Just in case it helps someone… . If you don’t have/want gulp/grunt/etc… or an extra shell script to proxy out your task commands , “npm run” is there already . this is for webpack and mocha as in “Build and Test” , Shift+Ctrl+B, Shift+Ctrl+T .vscode/tasks.json: { “name”: “npmTask”, //… “suppressTaskName”: true, “command”: “npm”, “isShellCommand”: true, … Read more
Now you can configure Visual Studio Code (version 0.10.2, check for older versions) to use existing git installation. Just add the path to the git executable in your Visual Studio Code settings (File -> Preferences -> Settings) like this: { // Is git enabled “git.enabled”: true, // Path to the git executable “git.path”: “C:\\path\\to\\git.exe” // … Read more
You can use language specific settings to enable it for a specific language only, e.g. JavaScript: “[javascript]”: { “editor.formatOnSave”: true } To disable it for a specific language, you could switch the global default to true and combine it with a language-specific false: “editor.formatOnSave”: true “[javascript]”: { “editor.formatOnSave”: false } Note that language specific settings … Read more
Temporary Exclusions From the search function, click the ellipsis to show the files to include and files to exclude text boxes. Enter any files and folder to exclude (separated by commas). Persistent Exclusions From menu choose File ➡️ Preferences ➡️ Settings ➡️ User/Workspace Settings and filter default settings to search. User settings will apply to … Read more
I had same/similar problem two days ago. @use is a new directive introduced in the new official Version ‘Dart Sass’ and replaces ‘@import’ which is depricated now. The popular Extension ‘Live Sass Compiler’ in VS Code is not longer supported by the maintainer for some time. So unfortunately the Sass Version is not updated in … Read more
I found the solution that partially works, but it may not be applicable to other software. The steps below are for Visual Studio Code: Install the NPM package containing type definitions for GAS using https://www.npmjs.com/package/@types/google-apps-script In your locally-saved script, create a ‘.js’ file and type import ‘google-apps-script’;