You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Migrate from vscode-nls/vscode-nls-dev to vscode-l10n #13145
The underlying libraries that facilitate string localization in VS Code extensions (vscode-nls/vscode-nls-dev) have been replaced with a new library: vscode-l10n.
The current vscode-nls appears to be causing the performance issue at #14549, which is about a 1 second synchronous block of CPU processing on startup, which supposedly would be fixed by switching to vscode.l10n / @vscode/l10n.
Activity
sean-mcmanus commentedon Jun 26, 2026
The current vscode-nls appears to be causing the performance issue at #14549, which is about a 1 second synchronous block of CPU processing on startup, which supposedly would be fixed by switching to vscode.l10n / @vscode/l10n.