November 2017 (version 1.19)
Update 1.19.3: The update addresses issue 42144 where the Workbench failed to load when having the Running Extensions view opened and profiling.
Update 1.19.2: The update addresses these issues. This update also includes a fix for an Electron security vulnerability. To learn more details about the applied mitigation, see this blog post.
Update 1.19.1: The update addresses these issues.
Note: As a result of fixing issue 40351, we now require you to pass "
-" as an argument to explicitly signal that the output of a piped command is coming in through
stdin. For example:
echo Hello World | code -(Windows) and
ps aux | grep code | code -(macOS, Linux). This is a breaking change from
1.19.0, please update any scripts that make use of this functionality.
Downloads: Windows | Mac | Linux 64-bit: .tar.gz .deb .rpm | Linux 32-bit: .tar.gz .deb .rpm
Welcome to the November 2017 release of Visual Studio Code. As announced in the November iteration plan, the focus this month was on GitHub issue clean-up, product performance, and data collection tools for better issue reporting.
During this iteration, we closed 4400 issues (either triaged or fixed) across all our VS Code repositories. As we busily closed issues, you did not stop filing new ones and you created around 2700 new issues. This resulted in a net reduction of around 1700 issues of which 1400 were in the main vscode repository.
Bug fixes as well as community PRs still resulted in a great list of updates. Here are some of the release highlights:
- Performance - Faster startup and other performance improvements.
- Serviceability/Diagnostics - New VS Code diagnostics, logging, and extension monitoring.
- Smarter IntelliSense - IntelliSense remembers your previous suggestion choices.
- Better Tab layout - Tabbed headers can scale to fit the available space.
- Git side-by-side image diff - Git source control provider can display image changes side by side.
- Pipe output into VS Code - Easily view terminal output in a VS Code editor.
- New debugging recipes - Learn how to debug Next.js, Meteor projects and applications using the nodemon utility.
If you'd like to read these release notes online, go to Updates on code.visualstudio.com.
You can also check out this 1.19 release highlights video from Cloud Developer Advocate Brian Clark.
The release notes are arranged in the following sections related to VS Code focus areas. Here are some further updates:
- Workbench - Compare your active file to the Clipboard contents.
- Editor - Folding improvements, interval line numbers, support macOS global Clipboard.
- Languages - TypeScript 2.6.2, JSX fragment syntax, new JSON with comments mode.
- Debugging - Undefine env variables per session, better VARIABLES rendering.
- Extensions - Choose which extensions are active in your workspaces.
- Extension Authoring - Pre-release extension support, yo code can enable TSLint and checkJS.
Insiders: Want to see new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available.
Performance is key to an editor and during November we fixed almost 50 performance-related issues. We spent significant time in the profiler and revisited the initialization phase of VS Code. Improving performance is not just about optimizing algorithms but also about improving perceived performance for the user. We began thinking about the startup life-cycle phases (#38080) to better order the creation of our components for faster perceived startup (for instance, always try to show a blinking cursor in the editor). To learn more about our performance work, you can review our issues labeled with perf-startup, perf-bloat (source code reduction), or perf.
Finally here are some noteworthy optimizations we'd like to mention:
- Improve startup and overall performance with an improved configuration-model #37426, #37539.
- Improve startup by caching extension information from
- Improve startup by delaying the creation of helper processes, like file watcher #38230, search app #38235, and extensions process #38323.
- Improve file loading for better startup performance #37541.
- Use the faster list widget instead of the tree when possible #38638. Rework the BREAKPOINTS view and the OPEN EDITORS Explorer section.
- Optimize the handling of touch events for improved performance #37917.
- Improve the overall workbench performance by skipping unnecessary layouts and computations 39699, #39185, #38966, #38963, #38962, #38960.
- Improve startup by removing unused code #38414.
And we are not done. Performance is a constant theme of the whole development team. Track our work with the perf-labels and don't be shy in filing performance related issues.
This release we also focused on VS Code serviceability in order to make it easier for you to provide us with the information we need to track down issues. We worked on logging, diagnostics, and extension monitoring to help you help us to make VS Code even better. Some of these features are still under development but we wanted to get these tools in your hands early.
VS Code now creates activity log files which can help diagnose unexpected issues like crashes, delays, etc.. When running, VS Code creates four primary processes,
extension-host, and each process logs into its own log file. You can open each log file using the command Developer: Show Logs... which will open a process picker to select the specific process log file.
VS Code supports following log levels:
By default, VS Code is configured with
info level and logs
info and the levels above (
critical). You can change the log level using the command-line argument
--log <level> Log level to use. Default is 'info'. Allowed values are 'critical', 'error', 'warn', 'info', 'debug', 'trace', 'off'.
You can also turn off logging using the option
--status command-line option
A new command-line argument was added which prints some useful VS Code diagnostics information to the terminal. You can share this information with us in GitHub issues and we will have a better understanding of the state of VS Code at the time of the issue.
code --status from the command line while another instance of VS Code is running and, after collecting status, you will see a display like this:
The output includes information about the environment, all running processes, and the counts of some common file types in the workspace.
VS Code process view
As a by-product of the new VS Code command-line option
--status, we created an experimental extension vscode-processes that shows all child processes of VS Code in a custom view and dynamically updates as processes come and go. To better understand the role of those processes, the extension analyses the process arguments and labels the processes accordingly. The extension's CPU load and memory consumption is also shown in parentheses.
In addition, the extension tries to identify processes that can be debugged by VS Code itself and offers a debug action for those in the context menu. All processes can be terminated or killed from the menu as well.
This extension is still a prototype and so it is not yet available on the Marketplace but you can easily build the extension VSIX by running the following commands:
git clone https://github.com/weinand/vscode-processes cd vscode-processes npm install npm run package
Once the extension VSIX is created, use VS Code's Install from VSIX... command to install the extension.
To make it easier for users to detect faulty or poorly performing extensions, we added a Running Extensions view. This view shows all the extensions which are currently running along with useful performance information. With this view, users can also profile VS Code in order to detect which extensions take the most time and are a likely cause of performance issues. Run the Developers: Show Running Extensions command from the Command Palette to see this view.
Note: The Running Extensions view is still under development so expect to see updates in future releases. We'd also appreciate your feedback.
How to file performance and native crash issues
We have created guides for:
Performance Issues - tracking down and filing performance issues
Native Crash Issues - data collection techniques for native crashes
New editor tabs layout option
A new setting,
workbench.editor.tabSizing, was added to control how tabs should size depending on the space available in the outer container. The default (
fit) works as before and will always ensure that the tab shows the entire name of the file. If space gets too little, a scroll bar will appear.
You can change this behavior by setting this new option to
shrink. When there is little space available, the tabbed headers will shrink up to a minimum and thus make it less likely that a scroll bar appears.
Pipe output directly into VS Code
We added support to pipe the output of a terminal command directly into VS Code and have it open in an editor:
The encoding of the terminal will be determined by running the command
locale charmap on Linux/macOS and
chcp on Windows. You can also set a
VSCODE_CLI_ENCODING environment variable to specify the encoding manually.
Note: We will now open a temporary file for reading from stdin as soon as we detect that stdin is not connected to a terminal. If you are in a setup where you start VS Code via the shell script (
code.cmd) from an application that is not a terminal, please change that to start our executable directly instead.
Compare open file to Clipboard
Thanks to PR #37841 from Max Furman (@maxfurman), you can now compare the contents of the currently opened file with the contents of the Clipboard. The command is Compare Active File with Clipboard (command id
workbench.panel.location is deprecated
We have removed the
workbench.panel.location from settings and are now saving this in storage. All the previous functionality for moving the panel to the side is retained. More details about this change can be found here.
VS Code IntelliSense re-sorts suggestions as you type. This ensures that the most relevant suggestions are near the top. However, there are cases in which multiple suggestions match equally well, for example
con matches on
constructor equally well and lexicographic sort decides which suggestion is pre-selected.
In this release, we've updated IntelliSense to remember what you have selected in such cases. Select
const for the
con prefix once and it will be the top match in the future.
Sometimes when you are typing, you may accidentally mix up neighboring characters, for instance instead of
console, you might type
resutl instead of
result. We have made IntelliSense more relaxed and it will now try a few permutation when scoring suggestions.
In the sample above, IntelliSense favors the
console suggestion by changing
cons as that match is stronger than the match of
We have changed
Shift + Click on the folding icons to not only fold/unfold the corresponding section but also all its children.
New folding regions have been added for the following languages:
Note: If you don't remember a folding marker, type
# at the beginning of a line and you will get IntelliSense suggestions. Each language proposes completion proposals or snippets.
New folding commands have been added:
- Fold All Regions (⌘K ⌘8 (Windows, Linux Ctrl+K Ctrl+8)) folds all regions from markers (for example
- Unfold All Regions (⌘K ⌘9 (Windows, Linux Ctrl+K Ctrl+9)) unfolds all regions from markers.
- Fold All Block Comments (⌘K ⌘/ (Windows, Linux Ctrl+K Ctrl+/)) folds all regions that start with a block comment token (for example
Interval line numbers
Thanks to PR #37120 from David Weber, the setting
editor.lineNumbers can now be configured with the value
interval, which will cause VS Code to render the line numbers every 10th line.
Global find Clipboard on macOS
Thanks to PR #35956 from Melvin, the editor now integrates with the macOS global find Clipboard. If you search for something in VS Code or another native macOS applications and then switch to another, the find widget will contain the same text. This feature is turned on by default on macOS and you can disable it by setting
HTML now offers code completion for character entities, such as
&. To see the proposals, type
& in a element content or attribute value and invoke IntelliSense.
JSON with comments
A new mode JSON with Comments (jsonc) has been added to distinguish between JSON-like files that allow comments and JSON files that follow the standard JSON specification. All VS Code configuration files use the new mode and allow comments, while
.json files default to the standard JSON mode that will report comments as errors.
VS Code now includes TypeScript 2.6.2. This minor update fixes a few important bug fixes and tooling improvements.
JSX fragment syntax
TypeScript 2.6.2 also brings support for React 16.2's new JSX fragment syntax.
VS Code now displays TypeScript code style issues as warnings instead of errors. This applies to:
- Variable is declared but never used
- Property is declared but its value is never read
- Unreachable code detected
- Unused label
- Fall through case in switch
- Not all code paths return a value
Treating these as warnings is consistent with other tools, such as TSLint. These will still be displayed as errors when you run
tsc from the command line.
You can disable this behavior by setting:
Language Server Protocol
The language server protocol was extended with the following new feature: a completion context given access to the trigger character, more completion item and symbol kinds as well as markdown support for completion items and signature help. The protocol additions are available in the
4.0.0-next.x version of the client and server npm modules.
You can now view changes in your images, side by side, directly from your Git repository:
Edit Breakpoint command
We have added a new Edit Breakpoint... command to the BREAKPOINTS context menu. This will make it easier for users to edit the condition or hit count of breakpoints.
Undefining environment variables
Many debug extensions provide support for adding (or overriding) environment variables that are passed to the debug target. With this release, it is now possible to un-define (remove) a variable from the environment as well.
If an environment variable is set to
null, this variable will be removed from the environment before the debug target is launched. This makes it much easier to test and debug code that relies on a variable not being defined.
Please note that in this release, only the Node.js debugger supports this.
New rendering style for synthetic elements in VARIABLES
In the debugger's VARIABLES view, we now show "synthetic" elements in a subdued style to distinguish them from the real "data" received from the debugger or runtime. In this release, only the "range" nodes of big arrays are considered "synthetic" and are rendered in the subdued style. We expect that more debug extensions will opt into this feature in the future.
New debug settings
- A new setting
debug.showInStatusBarcontrols the visibility of the debug Status Bar item. Possible values are:
alwaysand the default
- A new setting
debug.openDebugcontrols the visibility of the Debug view. Possible values are:
openOnSessionStartand the default
Enable extensions per workspace
VS Code has had support for disabling extensions globally or per workspace. However, there was also demand for enabling extensions per workspace. With this release, you can configure extensions to run only for specific workspaces.
There is new set of Java topics showing how to use the Java Extension Pack for debugging, cloud deployment, and Azure Functions development.
Python also has its own section where you can find tutorials for the Microsoft Python extension. There are topics starting with 'Hello World', moving on to debugging, linting, and unit testing.
We've added several new debugging recipes:
See Debugging Recipes to learn more about these guides and find helpful blog posts.
You can now distribute extension VSIXs with pre-release versions like
x.y.z-beta and VS Code will detect them and provide updates according to their version increments as defined here. Refer to this issue to learn more.
Extension generator -
strict TypeScript compiler options.
Debug API updates
Preview: Breakpoints API
In this milestone, we've continued work on the Debug API related to breakpoints. It is now possible to access the set of all breakpoints of a workspace (
vscode.debug.breakpoints) and register for notification about added, removed, or changed breakpoints (
Please note that accessing breakpoints initially returns an empty array but triggers a subsequent
BreakpointsChangeEvent event that updates
vscode.debug.breakpoints to the correct set. So if your code relies on the correct set of breakpoints, don't forget to register for
The different types of breakpoints are represented as different subclasses of
Breakpoint. Currently supported are
FunctionBreakpoint. Use an
instanceof check to determine the concrete type.
Note: Currently this API is proposed, so in order to use it, you must opt into it by adding a
package.jsonand you'll have to copy the vscode.proposed.d.ts into your extension project. Also be aware that you cannot publish an extension to the Marketplace that uses the
Output text on Debug Console
The proposed Debug Console API from last month has been slightly modified and moved from "proposed" to "official". An extension can append text to the Debug Console with
vscode.debug.activeDebugConsole.appendLine(text). The deprecated
debug.logToDebugConsole will be dropped as soon as it is no longer used in any extension on the Marketplace.
Debug contributions in package.json
More fine-grained debugger activation events
If a debug extension uses a
DebugConfigurationProvider, it is important that the extension is activated early enough so that the
DebugConfigurationProvider can be registered before first being used.
The foolproof way to achieve this is by adding the
onDebug activation event to the
activationEvents section of the extension's
package.json. This works fine as long as the extension does not spend a lot of time in its startup sequence. If it does,for instance starting a language server, early activation must be avoided because it could negatively affect other debug extensions.
To simplify startup, we have introduced two more fine-grained activation events:
onDebugInitialConfigurationsis fired just before the
provideDebugConfigurationsmethod of the
onDebugResolve:typeis fired just before the
resolveDebugConfigurationmethod of the
DebugConfigurationProviderfor the specified type is called.
Rule of thumb: If activation of a debug extensions is lightweight, use
onDebug. If it is heavyweight, use
onDebugResolve depending on whether the
DebugConfigurationProvider implements the corresponding methods
Debug Adapter Protocol
New enum value
virtual for the
presentationHint.kind attribute of type
The new enum value
virtual indicates that the variable is a synthetic object introduced by the debugger for rendering or user interaction purposes. The client is expected to render this element in a different way then regular variables.
Support for removing variables from the environment
runInTerminal request is used by a debug adapter to launch a debug target in an integrated or external terminal. One parameter to the request is the set of environment variables to pass to the debug target. In this release,
null has been added to the environment variable's value type with the semantics "remove the environment variable from the environment before launching the target".
We now use Yarn to manage our production and development dependencies. This has greatly reduced the setup time to prepare a VS Code repository, both for development and build. More details are in this Pull Request.
|Open Raw Default Settings||
|View: Toggle Tab Visibility||
|⌃0 (Windows, Linux Alt+0)||View: Open Last Editor in Group||
|⌘K C (Windows, Linux Ctrl+K C)||Compare Active File with Clipboard||
|Refresh Search results||
|Collapse Search results||
|Clear Search results||
- 36491: Backspace should not always cancel code completion
- 39594: Problems with nested snippet insertion
- 11928: Possible to bring up multiple dialogs on same dirty file when closing
- 31667: Configuration values are missing from files on remote network drives
- 18733: Dragging a tab can show visual glitch when tab not fully visible
- 16690: Closing tabs using mouse wheel click turns cursor into auto scroll
- 30530: Keyboard Shortcut to Skip Preview Using Quick Open
- 17552: Switch to Unsaved Tab When Prompting to Save
- 15477: Support dependencies for VSIX extensions
- 26871: Show a count badge for Problems panel
- 35580: Make "Workspace" and "Folder" settings more discoverable
- 38609: Install older version of an extension using VSIX
- 28331: Cache extension manifest files
- 38481: Use Yarn to manage dependencies
- 35749: Improve image view in working tree
Last but certainly not least, a big Thank You! to the following folks that helped to make VS Code even better:
- David Valachovic (@AdenFlorian): Support middle mouse click on folding decorator to recursively toggle folding PR #38727
- Ajit Singh (@ajitid): Update Quiet Light theme's JSX PR #39451
- Alberto Cortés (@alcortesm): fix Keyboard dispatch help message typos PR #36866
- Brook Riggio (@brookr): Update CONTRIBUTING.md PR #36673
- Dan Bovey (@danbovey): Update NumberBadge to show hundreds in full, thousands with k PR #38605
- Hannu Hartikainen (@dancek): Call shellscript files just "Shell Script" PR #36889
- David Weber (@DdWr): Add line number interval setting PR #37120
- Deric Cain (@dericcain): Added ability to use tilde as home dir in config for cloning repos PR #32222
- David Lechner (@dlech): Add firstline match for Makefile PR #38126
- Francisco Moreira (@Dozed12): Size down SCM discard icon PR #39135
- Ryan Lee (@drdgvhbh): add split pane to preferences editor PR #38000
- Carson McManus (@dyc3): fix debug console to handle more than one graphics mode in a single escape sequence PR #38981
- Louis MacFhionnlaigh (@ethernetcable): Change Twitter character limit PR #39109
- Harjyot Singh (@excerebrose)
- Fabio Spampinato (@fabiospampinato): Uninstall extensions given paths to their .vsix files PR #34042
- Felix Becker (@felixfbecker)
- Joel Kuntz (@Frozenfire92): Fix #39867 fix git popStash type check PR #39868
- Sanders Lauture (@golf1052): Show preview tag on extension page if extension is in preview PR #36261
- HUI ZHOU (@huizhougit): Set placeholder text in SourceControlInputBox PR #29822
- Anton Vildyaev (@hun1ahpu): Fix 37385 by introducing addition configuration setting PR #37704
- Ignacio Nicolás Rodríguez (@ignacionr): Update taskTemplates.ts PR #37905
- Yuki Ueda (@Ikuyadeu): Fix Markdown quote syntax highlight(fix #38523) PR #39487
- Itamar (@itamark): Capitalizing Contains in Contains changes PR #37980
- Justin Horner (@justinhhorner): Add Rename Branch to Git Extension PR #32244
- Karthik Iyengar (@karthikiyengar): Allow user to cancel cloning a git repo #30057 - WIP PR #32119
- MXI (@KillyMXI): Add Region folding for CSS (#_3422) PR #37789
- Markus Igeland (@Markussss): Added support for sorting multiple selections PR #36652
- Joe Martella (@martellaj): Adds "Accept All Current" to command palette PR #38582
- Max Furman (@maxfurman)
- Max Schmitt (@mxschmitt): "Cannot read property 'filter' of undefined" in extensionGalleryService PR #38642
- Melvin (@melvin0008): Add support for macOS globalFindClipboard #11233 #28896 PR #35956
- Jared Moore (@moorejs): Open File Handler now untildifies. Fixes #32736 PR #39122
- Nehal J Wani (@nehaljwani): Make v8-profiler, css-parser URI http-proxy friendly PR #38181
- Zanidd (@ninijay): Add platform info in code --version #37793 Done PR #37824
- @nkofl: Add code folding #region support in coffeescript PR #39334
- Tomer Ohana (@ohana54): Add .nvmrc file PR #39814
- Manuel Sommerhalder (@oncode): Trim whitespace from command.stash PR #39264
- Nathan Shively-Sanders (@sandersn): Fix array syntax in debugViewer.ts PR #37542
- Shivam Mittal (@shivammittal99)
- Shobhit Chittora (@shobhitchittora)
- Suhas (@suhasdeshpande): Update monaco-editor-setup.js PR #38130
- Sye van der Veen (@Syeberman): Auto-closing quotes in Python raw string literals PR #35636
- Ethan Woodward (@Takadimi): #36562 Sort multiple selections PR #37196
- Martin Thierer (@thierer): Compare to correct Ressource-URI when fetching content PR #34690
- Thomas Struller-Baumann (@Thomas-S-B): Removed unnecessary comma. PR #38104
- @tsalinger: Reuse last commit message for amend PR #38865
- Alexander (@usernamehw): Fixes #38691 PR #38692
- Yang Liu (@zesik): Ensure Replace box's width when showing PR #36902
- Remy Suen (@rcjsuen):
- Brett Cannon (@brettcannon):
- Maxim Reznik (@reznikmm): Formating is done by server, not by client PR #316
- Sven-Hendrik Haase (@svenstaro): Some grammar and consistency fixes PR #311
- Vlad Dumitrescu (@vladdu): Specify response from client/unregisterCapability PR #331
- Waleed Khan (@arxanas): Clarify response ordering (#_306) PR #333
- Darin Morrison (@freebroccolo) Fix docs for TextDocumentItem.create PR #269
- Mickael Istria @(mickaelistria):
- @amiramw typo fix PR #339
- Peter Burns (@rictic): Document that onWillSave handler capabilities reqs PR #275
- @danixeee: Return value after executing command request PR #284
- Gunnar Wagenknecht (@guw): Allow testing against latest Insiders app (#_89) PR #89
- kimushu (@kimushu): Fix invalid permission on Linux (#_84) PR #84
- Adam Miller (@amiller-gh): Add attrib namespace to parser PR #50
- Ludovic Oger (@garconvacher): Add DPub-ARIA roles (Digital Publishing WAI-ARIA Module 1.0) PR #14
- Sindre Svendby (@SindreSvendby): Accept .mjs as a valid fileending PR #161
- Morten N.O. Nørgaard Henriksen (@raix)
- Sebastian Silbermann (@eps1lon): Fixed link anchor PR #301
- Joachim Seminck (@jseminck): Fix typo: Rename udpate* to update* PR #293
- Seth (@osdavison): Fix incorrect link PR #291
- Maximiliano Céspedes (@neomaxzero): update Next-Js link PR #42
- John Pankowicz (@johnpankowicz): Added recipe for AspNetCore.SpaTemplates PR #41
- Cengiz Ilerler (@cilerler): updated deprecated command PR #32
This is the eighth month since we opened community localization in Transifex. We now have nearly 600 members in the Transifex VS Code project team. We appreciate your contributions, either by providing new translations, voting on translations, or suggesting process improvements.
Here is a snapshot of top contributors for this release. For details about the project including the contributor name list, visit the project site at https://aka.ms/vscodeloc.
- French: Antoine Griffard, Bruno Lewin, Maxime COQUEREL.
- Italian: Alessandro Alpi, Piero Azi, Aldo Donetti.
- German: thefreshman89, Carsten Kneip, Dejan Dinic, Volkmar Rigo, Max Schmitt.
- Spanish: Roberto Fonseca, Raul Rama, Alberto Poblacion, Carlos Mendible, Thierry DEMAN-BARCELO, Andy Gonzalez, Juan Ramón Rodríguez, David Triana, Pedro Sánchez, Jorge Serrano Pérez.
- Japanese: EbXpJ6bp, Tomoaki Yoshizawa, Yuichi Nukiyama, tanaka_733, 杉田 寿憲, Yoshihisa Ozaki, Hiroyuki Mori, Miho Yamamoto, Yuki Ueda.
- Chinese (Simplified): Joel Yang, 王东程, Wang Weixuan, 陈嘉恺, bingzheyuan, YF.
- Chinese (Traditional): Duran Hsieh, Winnie Lin, Kirk Chen, Ke-Hsu Chen.
- Korean: Ian Y. Choi.
- Hungarian: Tar Dániel.
- Portuguese (Brazil): Roberto Fonseca, Bruno Sonnino, Lucas Miranda, SQLCrespi, Alefe Souza, Felipe Caputo, Danilo Dantas, João Holanda, .
- Portuguese (Portugal): BlueKore, António Campos, Ruben Mateus.
- Turkish: Adem Coşkuner.
- Bulgarian: Любомир Василев, Didi Milikina, Bozhidar Gevechanov, Ilia Iliev.
- Dutch: Maarten van Stam, Armand Duijn, Senno Kaasjager, Elmar Jansen, Gerjan, Gerald Versluis, Peter Hut.
- Indonesian: Joseph Aditya P G, Hendra Setiawan, Febrian Setianto (Feber), simplyeazy, Septian Primadewa, Riwut Libinuko, Alfa Phi.
- Polish: Wojciech Maj, Patryk Adamczyk, Patryk Zawadzki, Sölve Svartskogen, Mateusz Wyczawski, KarbonKitty, Marek Kurdej, Adam Borowski, Paweł Sołtysiak, Jakub Drozdek.
- Serbian: Darko Puflović, Марко М. Костић, Nikola Radovanović.
- Swedish: Joakim Olsson.
- Tamil: rajakvk, Praveen, Karunakaran Samayan, Nadar Solomon Sunder.
- Thai: Sirisak Lueangsaksri, Yuttana Buasen.
- Ukrainian: R.M., Oleksandr, Bogdan Surai, Borys Lebeda, Yevhen Kuzminov.
- Vietnamese: Thanh Phu, Khoi Pham, Hung Nguyen, Vuong, Trung Đào.