Improve the TypeScript lint/intellisense experience #573
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #569, where some of the dev-env challenges were discussed with @gregtatum.
With these changes, the
lint
task is no longer dependent onbuild
and intellisense works immediately for internal cross-package dependencies.The dependency of
test
onbuild
remains, and it's turning out to be more difficult without in-depth changes. Briefly, Mocha does not offer an out-of-the-box path aliasing as e.g. TypeScript'spaths
or Jest'smoduleNameMapper
. This means that something like a Babel plugin would need to be registered for tests, as well asts-node
for handling the TypeScript sources. Alternatively, all of the tests could be ported to Jest and/or TypeScript. That sounds like more work than it's worth at this time.