Andrew Bradley

Make sure you're looking at the correct version tag in GitHub, matching the npm version you're looking at. On Sat, Jul 4, 2020, 2:36 PM Vladimir Grenaderov wrote: > @cspotcode...

Does node have any equivalent functionality? This is a chunk of added complexity, so ideally node or a third-party library already provides this, and we simply maintain compatibility. I suspect...

I want to try rolling stuff like this into #1204, to avoid needing extra logic for lots of env vars. And we'll get env var support for new flags for...

Labelled "help wanted" to indicate we will wait for a pull request.

I stumbled upon some TS compiler API functionality that's relevant here: ```typescript const classifier = ts.createClassifier(); const classifications = classifier.getEncodedLexicalClassifications('const a = 123;', ts.EndOfLineState.None); for(let i = 0; i <...

Thanks for this. Because of the American holidays, I have somewhat of a backlog of issues and PRs which need attention before I'll be able to properly review this. There...

> If you have configured the paths compiler option and you are using it in your code, your code will only run if the path mapping is enabled. Good point....

Fair point. Would it be a great hardship for those users to disable tsconfig-paths? I hope they would appreciate the simplicity of removing a component. I would like our default...

I made an attempt at adding the CommonJS resolver hook. Still some outstanding TODOs that I need to address, but this is looking good.

Looks like we have test failures on Windows due to module specifiers using forward slashes and windows paths using backslashes. I haven't checked the code yet, but we probably have...