Interestingly, in the URL CLI article, you mentioned the difficulty of maintaining such bookmarklets. That was a huge motivator for bookmarkl.ink. You can keep your verbose, commented code in a gist while the actual bookmarklet is tree shaken, stripped of comments, minified, and encoded. As of late, you even get some creature comforts like TypeScript support. Finally, every gist is a repo behind the scenes so you get version control for free.
ohhh I thought it was primarily a repository for people to browse each other's bookmarklets, I am going to check it out if it would let me do my management in a more sane manner! I am still using the system in that blog post with regex and deletion+reimporting when I need to update several at a time (which is not that uncommon) and I still hate it haha
- https://bookmarkl.ink/ashtonmeuser/a36be4b6c835276f1a22a8c49...
- https://bookmarkl.ink/ashtonmeuser/a36be4b6c835276f1a22a8c49...
- https://bookmarkl.ink/ashtonmeuser/a36be4b6c835276f1a22a8c49...
Interestingly, in the URL CLI article, you mentioned the difficulty of maintaining such bookmarklets. That was a huge motivator for bookmarkl.ink. You can keep your verbose, commented code in a gist while the actual bookmarklet is tree shaken, stripped of comments, minified, and encoded. As of late, you even get some creature comforts like TypeScript support. Finally, every gist is a repo behind the scenes so you get version control for free.