The condense tool can be used as a base for something like this, but
at the moment Tern itself does not help with automatically creating,
using, and updating such condensed definitions.
The Tern server does update only what needs to be updated, but it
periodically starts (in the background) a full re-analysis because the
type graph tends to deteriorate when it is patched up a bunch of
times. For giant projects, this will be expensive. For giant projects,
this is expensive. But for giant projects, the current approach is
problematic anyway, for memory-use reasons, so the approach you
outline would be better.
One approach would be to start a new project which wraps a Tern
server, exposing the same interface, but generating and using
condensed versions of files in the background. The tricky part is
figuring out which sets of files to treat as 'units' to be condensed
together. If you're using node-style packages, you could maybe use
these as units.
Best,
Marijn
> --
> You received this message because you are subscribed to the Google Groups
> "tern-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
tern-dev+u...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.