microsoft / microsoft/vscode-makefile-tools
Migrate from `vscode-nls/vscode-nls-dev` to `vscode-l10n`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
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.
https://github.com/microsoft/vscode-nls
https://github.com/microsoft/vscode-nls-dev
https://github.com/microsoft/vscode-l10n
Opening this issue to track migrating to the new library.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the repository's current localization usage with the linked vscode-nls, vscode-nls-dev, and vscode-l10n projects. Identify all affected entry points and tests, then confirm that migration to vscode-l10n preserves the extension's localized strings and build behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, localization
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100