split helix-shared

[tripodsan]

although it's nice that we have a helix-shared for all purposes, it still generates a lot of downstream updates for projects that don't even use the feature that was updated.

IMO, this was acceptable, when with only a handful of projects, but with 20-30 projects, this become expensive.

I suggest to follow lodash's model and release each feature as an own npm package.

package	feature
@adobe/helix-shared	entire helix share package
@adobe/helix-shared-git	git url and utils
@adobe/helix-shared-config-helix	helix config, strains and condition
@adobe/helix-shared-config-index	index config
@adobe/helix-shared-config-mount	mount config
@adobe/helix-shared-config-redirect	redirect config
@adobe/helix-shared-config-markup	markup config
@adobe/helix-shared-utils	utils
@adobe/helix-shared-utils	string utils
@adobe/helix-shared-dom	dom utils
@adobe/helix-shared-async	async utils

however, semver needs to be individual for each release package, otherwise a modification in package A would bump all other packages, and nothing is won.

[adobe-bot]

🎉 This issue has been resolved in version 8.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀