Node plugin: dynamic resolution of the module name

[Paulo Vieira]

Hello all!

In my node code, I require my private modules as such

```

 var utils = require(global.rootPath + "server/common/utils");

```

This way Tern fails to lookup the module correctly. But it's fine If I use a relative directory, such as

```

 var utils = require("../../server/common/utils");

```

Is there anyway to make Tern find the module using the first way? Or would you recommend some workaround (such as setting some environment variable)?

Thanks for any help!

[Marijn Haverbeke]

Tern currently has no way to figure out the value of non-static
strings, and thus will not resolve dependencies required in this way.
There is no workaround.

> --
> 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.