build: configure package to build and publish from dist directory #69
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.
Similar to watson-developer-cloud/node-sdk#990, this updates the build process for the repo to build the files to a
dist/
directory instead of inline next to the source files. I add tsc-publish (which I maintain) to then help handle getting the right files (based off the.npmignore
file) into thedist/
folder when you go to publish (through semantic-release).To validate behavior and close the loop, I then did the following:
to produce the masterodin-cloud-sdk-core package (which I will unpublish in ~70 hours) and then swapped out the
ibm-cloud-sdk-core
package with this one innode-sdk
and successfully passed anpm run test
there.Checklist
npm test
passes (tip:npm run lint-fix
can correct most style issues)