I have a preference of having my imports alphabetized by package name.
You're absolutely welcome to ask me to revert those changes, it's just
a preference of mine. I updated the build command to use the specific
tsconfig.build.json that will allow for the base tsconfig.json to
reference all ts files, while the build one only references the src
directory. Also switched out rm -rf for rimraf to take into account
those who may be on windows (and as the package was already installed).
All tests still pass, and the Node REPL pulls in the correct functions
when using require('./').
Hi @jmcdo29 and @johnbiundo, I'm running into the same problem as #9, the dist folder wasn't included in the npm package. Can we got this PR merged and publish a new version?
chore: clean up imports and configs
I have a preference of having my imports alphabetized by package name. You're absolutely welcome to ask me to revert those changes, it's just a preference of mine. I updated the build command to use the specific
tsconfig.build.json
that will allow for the basetsconfig.json
to reference all ts files, while the build one only references thesrc
directory. Also switched outrm -rf
forrimraf
to take into account those who may be on windows (and as the package was already installed). All tests still pass, and the Node REPL pulls in the correct functions when usingrequire('./')
.fix #9