* [monorepo] lint .mts/.cts files
ESLint's `files` globs listed `{js,jsx,mjs,cjs,ts,tsx}` but never the
module-scoped TypeScript extensions, so every `.mts` file in the repo was
silently skipped with "File ignored because no matching configuration was
supplied" -- 21 files today, all in services/web, and more as backend code
migrates to TypeScript (`.mts` is the extension runtime-loaded backend TS
has to use, since services/web has no `"type": "module"`).
Each extension list now carries the c/m variants of the languages it
already allowed, canonicalised to one of:
{js,cjs,mjs} JS only
{js,cjs,mjs,jsx} JS + JSX
{js,cjs,mjs,ts,cts,mts} JS + TS, no JSX
{ts,cts,mts,tsx} TS only
{js,cjs,mjs,jsx,ts,cts,mts,tsx} everything
No list gains a language it did not already have, and none gains JSX
where it was previously excluded, so backend globs keep excluding
jsx/tsx and TS-only rule blocks keep excluding JS.
Both the extension declaration and the plugin/parser block in
services/web/eslint.config.mjs are widened together: widening only the
rule blocks makes `@overleaf/*` rules match files the plugin
registration does not, which fails with "could not find plugin
@overleaf".
The root global-ignores shim (`services/**/*.{mjs,cjs,ts,tsx}` and
friends) is deliberately left alone -- it replicates ESLint v8's file
walker so pre-existing debt in never-linted files stays off the build.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Fix eslint errors
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
GitOrigin-RevId: 084d0d054db9db6b5e3dd26de56d14358ab5edf7
Lezer-LaTeX, a LaTeX Parser
Lezer-LaTeX is a LaTeX parser implemented with lezer, the parser system used by CodeMirror 6.
The parser is written in a "grammar" file, (and a "tokens" file with custom tokenizer logic) which is then compiled by @lezer/generator into a parser module and a "terms" module. The parser module is then loaded by the CodeMirror 6 in the web frontend codebase.
Important files
-
Source files:
./latex.grammar: The grammar file, containing the specification for the parser./tokens.mjs: The custom tokenizer logic, required by some rules in the grammar
-
Generated files:
./latex.mjs: The generated parser./latex.terms.mjs: The generated terms file- (these files are ignored by git, eslint, and prettier)
-
Scripts:
web/scripts/lezer-latex/generate.js: A script which runs the generator on the grammar, producing the generated parser/terms filesweb/scripts/lezer-latex/run.mjs: A script that runs the parser against a supplied file, and prints the tree to the terminal
-
Webpack plugins:
web/webpack-plugins/lezer-grammar-compiler.js: A webpack plugin that calls the generator as part of the webpack build. In dev, it will automatically re-build the parser when the grammar file changes.
NPM tasks
-
lezer-latex:generate: Generate the parser files from the grammar- (Calls
lezer-latex/generate.js) - This should be run whenever the grammar changes
- (Calls
-
lezer-latex:run: Run the parser against a file- (Calls
lezer-latex/run.js)
- (Calls
Generating the parser
From the monorepo root:
# automatic (on changes)
make install
# manually
bin/yarn -w services/web run 'lezer-latex:generate'
Tests
Unit tests for the parser live in web/test/unit/src/LezerLatex. There are three kinds of test, in three subdirectories:
corpus/: A set of tests using lezer's test framework, consisting of example text and the expected parse treeexamples/: A set of realistic LaTeX documents. These tests pass if the files parse with no errorsregressions/: Likeexamples/, these are expected to parse without error, but they are not realistic documents.
These tests run as part of test_frontend. You can run these tests alone by invoking:
make test_unit TEST_NAME_PATTERN='lezer-latex'
Trying the parser
While developing the parser, you can run it against a file by calling the lezer-latex:run task. There are
some example files in the test suite, at web/test/unit/src/LezerLatex/examples/.
For example:
bin/yarn -w services/web run 'lezer-latex:run' web/test/unit/src/LezerLatex/examples/amsmath.tex
If you omit the file path, the default file (examples/demo.tex) will be run.
Integration into web
The web frontend imports the parser (from latex.mjs), in frontend/js/features/source-editor/languages/latex/index.ts.
The parser is then plugged in to the CM6 language system.
The web build
In web/Dockerfile, we have a RUN command that calls lezer-latex:generate as part of the build. This is necessary to ensure the parser is built before the CI tests run (notably: we can't do the build during the tests, because we can't write to disk during that stage of CI).