Show installed component version in the client

[blackfalcon]

Shared Discussed in #511

Something that has come up repeatedly is that users would LOVE to know the version of the element loaded into the client and showing in the UI.

The ask is, how can we do this? An attempt to do this was made with this feature update to auro-button where the version was used as an attribute in the DOM.

That felt like a good idea at the time, but maybe we do something different like have this print in the console?

One issue that was never resolved was that the bundled version was always a release behind because the bundled version's package.json was NOT updated after the release as this is an additional commit to the repo. A possible solution is to use a dry run.

[blackfalcon]

The following update was added to the WC Generator. This and an update to the ./generateDocs.js file that supports the Version variable.

WC-Generator/componentDocs/partials/usage/bundleUseModBrowsers.md

Line 5 in 2755e1d

<script src="https://cdn.jsdelivr.net/npm/[npm]/[namespace]-[name]@[Version]/dist/[namespace]-[name]__bundled.js" type="module"></script>

Additionally, there was an update to the ./package.json file that supports additional builds in the remote and then commits these updates back to this repo after a new version release.

WC-Generator/template/package.json

Lines 112 to 119 in 2755e1d

	"assets": [
	"./package.json",
	"./CHANGELOG.md",
	"./README.md",
	"./docs/api.md",
	"./demo/demo.md",
	"./demo/apiExamples.md"
	]

WC-Generator/template/package.json

Line 159 in 2755e1d

"postversion": "npm-run-all build:api build:docs"

What is happening here?

These updates do a handful of things. Leveraging semantic-release, in the remote, a build happens. This build performs a handful of actions in preparation for release. One is, after evaluating the commit message, semantic-release preps the next semver. The postversion script in ./package.json will inject these script commands PRIOR to the release, and then commits back to the repo.

It's at this time that the ./package.json version is updated. Running the builds here takes the value of the ./package.json and then applies it to the Version variable that ./generateDocs.js can use.

Ideally, we can add any build step here to accomplish this feature. These updates would address the issue of version management commented in the discussion and this does not require the use of dry-run.