Blake Embrey

That’s how this module works but it doesn’t tell you if it’s already been registered - anything could be on those extensions already. A global would be the most appropriate...

@ZSkycat Your assumptions are incorrect here. Just because someone has registered `.ts` and `.tsx`, that does not mean there'll be issues. Anything could be registered, such as some function that...

@gmathieu Sorry about that. It's a tricky problem, can you turn it off in karma? When the error gets added to avoid re-registering, it might cause some trouble for you...

There’s actually already a global symbol now that could be used. The reason I haven’t done this issue is because it’s a little more complex - you need to check...

1. I don't think so, though I can replicate project references working for other cases. It's using the language services API today which has typically had no problems, but I'd...

@kerdany Thanks! Interestingly I get the same error in development with VS Code and `tsc`, until I enable `--build`. This makes sense, since I assume that TypeScript is actually building...

Another interesting part of this is that it's related to `node` and TypeScript's understanding of module resolution. You can actually make this work with the current release of `ts-node` by...

This sounds really great! Is the main blocker right now the second issue? I assume the first one is workaround-able or we can put this behind a flag until we...

You're correct for the intended usage, though I don't think you broke it. I feel like I broke it when trying to refactor for TypeScript incremental compilation or something. Not...

@donaldpipowitch Why not just use the `extends` feature as recommended in your PR (https://github.com/palantir/tslint/issues/2163#issuecomment-293416322)?