feat: added tree-shaken bundler-friendly scripts

[jurerotar]

Continuation of #168, which was accidentally closed.

[tomayac]

Just let me know whenever you want to merge this.

We still have this settings bug where apparently no one can grant access anymore. I don't get it.

[tomayac]

I looked a bit more into it, @sqlite to my surprise is not an organization, but a regular user account. @sgbeal, do you or Richard have the keys to that? Right now, these accounts have access, but only @sqlite can actually grant new users like @jurerotar access, and, as we're at it, should convert the account into an organization, so it can properly be managed.

Collaborators:

• @sqlite: admin
• @tomayac: write
• @sgbeal: write
• @schickling: write
• @mmomtchev: write

[jurerotar]

Just let me know whenever you want to merge this.

Will do! I still need to expand the test suites to cover all of this. I also want to expand the docs, the README is about to get very long with these new exports added, so I want to clean it up a bit 😄

[sgbeal]

I looked a bit more into it, @sqlite to my surprise is not an organization, but a regular user account

Right - Richard set that up ages ago for the fossil-to-git export. He's the only one with access to it. i'm now wondering whether we should create a new account, like sqlite.org, as an organization? (Edit: or is it possible to convert the account to an organization?)

All @-mentions of sqlite end up in the sqlite support mailbox but we invariably ignore them because everyone and their dog makes commits like bump @sqlite to version X and they don't realize that they're notifying us every time that happens. i'll point drh here to get his input on it - he doesn't appear to have an account here beyond the sqlite one. (edit: will wait until i've got more info about our options.)

[tomayac]

If there's a way to convert the user account sqlite into an organization and rename it to @sqlite.org on the way, this would be ideal, as it means all links would be redirected at the GitHub level. If this isn't possible, then I'd likely keep the old name, just converted to an organization.

[jurerotar]

GitHub now also gives the option to disable PRs on a repository, so you can do that to on upstream repo to remove some more of the noise 😄

[sgbeal]

i'll point drh here to get his input on it - he doesn't appear to have an account here beyond the sqlite one. (edit: will wait until i've got more info about our options.)

drh is currently swamped with higher priorities, so i won't bother him with this just now but am flagging it in my calendar to bring up when his schedule opens up (unlikely to happen before calendar week 40).

Re. disabling PRs - we just ignore them but i'll point out this option to him.