domlink: it links your javascript shit to your dom shit! or at least simplifies stuff? idk.
i dont want to wrestle npm if i can help it.

nah, we trashing the browser crap.
"imma do my own thing" *makes something that looks like dogshit*
(it's anti-css, anti-html. if that makes sense. we dont do fancy 'round these parts.)
ok maybe a little css

"watch this its gonna be jquery 2" famous last words

in case its not obvious i dont remove anything from this file because its entertaining
i oughta post this up on tangled or something (sorry if your eyes bleed)
also i want to say that like this isnt a super serious project like fyi whoever reads this.

>i dont want to wrestle npm if i can help it.
lol lmao i really thought i could get away with a single pure js file

hey! heads up! im just thinking that as i add things someone might go "wow i want to use that"
i dont know how packaging works (yet). if you can somehow pull my code into your project as it stands, expect it to break.
its not good for your health. just dont. not yet?


> I have learned that the name you give something when you don't know
> what you should call it should always end up being the final name and
> that's also the case if objectively, it sucks.
- @poggers.website
at://did:plc:7ggpsji45es4auo5pqjmnarr/app.bsky.feed.post/3lx5d3p4oos2n

bro idk what this is anymore but im a fan of it and will keep going

i really gotta stop using Node.wraps...
that literally means that my implementation around it is inadequate

i hate git sometimes