fix: missing multi-select JS code in production build

[chrisarridge]

This is a really small quick fix to get the multi-select custom HTML element into the production build. It partially addresses #77 but does not make any changes to the storybook to add working example code.

[codemacabre]

Whoops, that was an oversight. Thanks for spotting this, @chrisarridge. I've requested a small change just for consistency, but otherwise approved.

[codemacabre]

@chrisarridge Rather than create a separate branch and PR, I thought I'd add on to this PR; hope that's okay.

I've updated the <multi-select> to also allow for <options> elements to be added as children, as well as the original implementation to add options programmatically, which on reflection wasn't the best way of using it (and as you noted, wasn't well documented). This should be much more intuitive and better documented now.

[github-actions]

🎉 This PR is included in version 4.5.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀