Jacob Hummer

I used a tricksy hack to make the cjs folder treat .js as .cjs by putting a `{"type":"commonjs"}` package.json in there 😆

@mesqueeb This is the next PR that I think should be tackled 😊

I note that you mentioned you want to keep this package relatively simple. I personally find the "dev" "production" branches highly confusing and over-complicated for what I assumed was the...

I also think that **removing dist from source control** is a good step to simplify the workflow of stuff too. That way you don't need to commit your build artifacts,...

**offtopic:** Another thing is potentially splitting each function into its own file. This would definitely encourage more writing in the JSDoc area since it's like "I need to write more...

> before I was thinking I'd need to have a production and dev branch separate so I can merge everything from `dev` into `production` once I wanna do a release....

> I like to be able to see what changes to the build pipeline actually change in the `dist` folder. I also like how easy it is for other devs...

Guess what! 🥳 I found a pretty good workflow that I think ticks all (_most_) the boxes for the version thing! 1. It's medium-ish automation. It's another `check-version-bump.yml` or similar...

Actually, my problem isn't the types. Its that this library is bundled as _two separate duplicate versions_: One of CJS and one for ESM when it _should_ probably be just...

> kinda... 🤔 😅 Let me try again 😆 hopefully this doesn't confuse you more lmao 1. You compile the code twice: one for MJS and one for CJS. 2....