We need someone with awesome Node-fu to help with this. :)

Here's the situation. We have ESLint and ESLintTester as two separate projects. ESLint has ESLintTester as a dev dependency for running tests. ESLintTester has ESLint as a dependency because it's basically creating integration tests for rules. That means when you checkout ESLint and npm link it, it installs ESLintTester, which in turn installs a local copy of ESLint that it uses for the tests. Likewise, when you checkout ESLintTester and npm link it, it installs a local copy of ESLint.

So if you are a core ESLint developer, you need to have both ESLint and ESLintTester checked out. Ideally, they would be able to just use each other instead of the npm-deployed versions. However, that doesn't seem to work for some reason.

This all works okay until we need to create a change in core ESLint in order to implement a rule, in which case we get a "method not found" error for any new method that was added to the core. And there's the rub: basically, new methods to the core of ESLint would need to be added and published, ESLintTester would then need to be updated to the latest ESLint and published, and the ESLint would need to be updated to use the latest ESLintTester.

This sucks.

There must be some way to make each project use the global links, but I just can't figure out how to do it.