Build ESM/UMD, publish to npm - #9
Open
bkeepers wants to merge 11 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
👋 @swevans, thanks for making this. I spent all day yesterday trying to figure out what changed in my project that was working a few days ago suddenly stopped working on my phone. Turns out I didn't have the mute switch on when I first built it, but I usually do. 🤦
I wanted to use this in my project, which pulls in dependencies via npm modules. So I made some tweaks to build ESM/UMD modules and published the iosunmute package to NPM.
I'm happy to either maintain this module as a fork, or give you access to publish, whichever you prefer.