fix tsc output and published package structure #18
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.
I saw #8 open and thought I could make an easy fix here. I've found it usually gets confusing when you want to transpile
src
->lib
yet want to reference values frompackage.json
at the project root or have test files outside of thesrc
root directory. The way I've seen it done is torootDir
andinclude[]
tosrc
resolveJsonModule
and userequire
, or leave it on and usefs.readFileSync
if you need json module types in other placesAside from that, I also noticed the use of .npmignore wasn't doing a great job—files like
.vscode/*
,fixtures/*
,tsconfig.json
, etc. were getting into the package tgz. I've removed it and added"files": ["lib"]
, this is safe because of how most npm clients include/ignore files by default.New package tree after these changes: