* Allow extensions to use new API and it get included in Language Packs
This leverages the l10n-dev package to analyze ts files for `l10n.t` calls.
* delete console.logs
* remove dead code from Transifex
* use @vscode/l10n-dev for XLF operations for extensions
* generated files
* more generated files
* remove dead code
* move l10n-dev to where gulp is
* generated
* Enforce ILocalizedString usage with f1 property via types
* complete comment
* Visit all symbols when encountering a union type
* use ILocalizedString
* fix tests
Co-authored-by: Alex Dima <alexdima@microsoft.com>
* perf - concatenate windows main files
* Revert "Revert "Use `esbuild` to bundle some CommonJS main files (#160957)" (#161118)"
This reverts commit 84c46b71a5.
* build - exclude server main files
* build - make concat a task that runs like the others
* some renames
* Avoid overwriting the nodejs closure require
* Revert "build - exclude server main files"
This reverts commit 736516624e.
Co-authored-by: Alex Dima <alexdima@microsoft.com>
* ensure node.js `require` is captured
* optimize `main.js` and `cli.js`
* cleanup
* leave out bundled files
* drop package.json from userdata paths
* fix web task
* fix editor distro
* inline version into `product.json`
* also bundle server
* t
* actually do server too
* Keep bundling nls in editor worker
Co-authored-by: Alex Dima <alexdima@microsoft.com>
* Remove vscode-notebook-tests in favor of an .ipynb in vscode-smoketest-express
* Update build folder
* Add build task to correct platform
* Build for smoke tests on other platforms
* Fix repo url and remove comment
* Just -media?
* Update darwin/win32 as well
Resubmission of #157532 with the following changes:
- Use `eslint-plugin-local` instead of `yarn` link to run our plugins
- Move our plugins to a top level `.eslintplugin` dir (as required by `eslint-plugin-local`)
- Update all names to `local/`
* Run our custom eslint rules using ts-node
Use `ts-node` to run our custom eslint rules. This lets us delete the pre-compiled js. It also means you can don't have to compile the rules while editing them
As part of this change, I've also switched us to using an eslint plugin instead of a rulesDir. This is now the preferred way to ship custom rules
* Fix two more disables
* Move ts-node to project root
* Enable transpileOnly
on Windows, my files are checked out with LF. the script which generates extensionApiProposals.ts always uses os.EOL, so it always is dirty on my repo every time I compile
