build: use npm pack
tarball for local examples and testing instead of .local
#859
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.
@ctavan, I don't expect this to be controversial but it'd be nice to get your sign off here since the ".local" directory setup was initially your idea.
Briefly, this does the following:
npm pack
tarball (in .build/uuid.tgz) that can be installed locallyNote
npm install
in the examples/* dirs was failing on GH test runners becausenpm pack
's output is platform specific. This tends to causenpm
to complain when it compares the checksum it sees on one platform (GH runner) to theintegrity
checksum it caches in package-lock.json on another platform (like our laptops). The workaround was to add the--no-package-lock
when installing in examples/* dirs. This isn't a big deal since the only thing being installed is theuuid
tarball. And it has the nice side-effect of removing the need for package-lock.json files in those dirs.