feat: add max_ts_server_memory initialization option

[ShayanAbbas1]

Problem

In large workspaces (e.g. Nx monorepos), the Angular language server exceeds node's default heap limit (~4 GB) while loading the project graph and crashes. Zed restarts it, it crashes again — an endless loop where template navigation and completions never work. In Zed's logs this shows up as escalating request timeouts followed by:

Get definition via angular failed: Server reset the connection
Broken pipe (os error 32)
... via angular failed: server shut down

On my Angular 19 monorepo (~10 apps, ~20 libs) the server died every ~3 minutes, 11 restarts in a day, and was effectively unusable. Other node-based servers in Zed already handle this — e.g. Zed launches eslint with --max-old-space-size=8192, and vtsls exposes maxTsServerMemory.

Change

Adds an opt-in max_ts_server_memory initialization option (in MB), passed to node as --max-old-space-size, following the same pattern as the existing angular_language_server_version / typescript_version options:

{
  "lsp": {
    "angular": {
      "initialization_options": {
        "max_ts_server_memory": 8192
      }
    }
  }
}

Left unset, behavior is unchanged.

Testing

• cargo build and cargo fmt -- --check pass.
• Installed as a dev extension and verified against the monorepo that exposed the problem: the server launches with --max-old-space-size=8192 and stays alive well past the point where it previously OOM-crashed; template go-to-definition works.
• README section added documenting the option.

[jpike88]

your pr has conflicts, pleaes resolve them thanks

[ShayanAbbas1]

@nathansbradshaw please review, i have tested it and am using the same workflow in my local dev. This would help with bigger projects.

[jpike88]

looks good to me

[jpike88]

@nathansbradshaw able to publiush a new version please thanks mate

[nathansbradshaw]

@jpike88 I think if you open a PR for the zed extensions, the Zed team will be able to help you get a new version pushed