Inject package version nimbly

We need to figure out a smarter way than stuffing package.json into clientside bundles (as of #57). How? It needs to work as npm module and as UMD bundle.

Start by inspecting package.json and the repository's current packaging setup. Compare how the project is consumed as an npm module versus a UMD bundle, and determine a version-injection approach that avoids placing package.json in client-side bundles. Done means both distribution forms expose the package version without bundling the full package metadata.

Written by the indexing model from the issue text.