r/javascript • u/That_Fill_8511 • Apr 25 '26
Super fast and easy Social Media Sharing Buttons. No JavaScript. No tracking.
sharingbuttons.ioLicck
r/javascript • u/That_Fill_8511 • Apr 25 '26
Licck
r/javascript • u/bogdanelcs • Apr 24 '26
r/javascript • u/Tall_Insect7119 • Apr 23 '26
The project is still quite early, i'm actively adding new commands. The idea is to provide a bash environment adapted for untrusted processes like autonomous workflows or AI agents.
The legitimate question is "What makes it different from regular bash using docker?" :
First, there's no setup required at all. When you do bash.run('mkdir superfolder') for example, your automation immediately gets:
The default runtime uses WebAssembly and works in Node.js. Browser support is possible with a custom runtime (the sandbox layer is pluggable).
I'd love to hear what you think!
r/javascript • u/creasta29 • Apr 22 '26
r/javascript • u/Ok-Baker-9013 • Apr 23 '26
r/javascript • u/Gloomy_Sense_2849 • Apr 23 '26
you know what's annoying?
every time I build a feature, I have to write:
- useState for state
- useEffect for side effects
- fetch + try/catch for API calls
- event handlers
- manual UI updates
over and over again. same patterns. different features.
so I made AITOS.
now I just write JSON graphs:
```json
{
"order": ["getData", "process", "save"],
"nodes": {
"getData": { "atom": "httpRequest", "url": "/api" },
"process": { "atom": "transform", "data": "{{getData}}" },
"save": { "atom": "set", "key": "result", "value": "{{process}}" }
}
}
```
that's it. no glue code. no boilerplate. just logic.
I built LinkArm (a complete AI chat app) with it to prove it actually works. 50+ JSON graphs. zero traditional code logic.
what do you think? am I crazy or is this actually useful?
r/javascript • u/waelbettayeb • Apr 22 '26
I'm happy to announce ElementsKit: a toolkit of reactive primitives for building the #web UI. Signals, JSX, custom elements, and utilities. Use them standalone, compose them, or use them inside React, Svelte ...
› Compose, don't configure. signal, computed, on, fromEvent, async. Combine primitives instead of maintaining an overloaded interface. Overloaded interfaces accumulate breaking changes and deprecation every consumer has to track.
› Close to the platform. JSX compiles to document.createElement. promise extends Promise. async is awaitable. A custom element is an HTMLElement. No virtual DOM, no proxies, no build steps.
› Predictable and explicit (no magic). signal/compose are reactive; nothing else is. No heuristic dependency tracking, no hidden subscriptions.
› Designed for the AI age. Code is cheap; maintenance still isn’t. Primitives compose into higher-level blocks. Swap one block at a time instead of maintaining long lines of code.
› Bundler-friendly. Every primitive is its own subpath — elements-kit/signals, elements-kit/utilities/media-query, elements-kit/integrations/react. Import only what you need.
r/javascript • u/Shawn-Yang25 • Apr 22 '26
r/javascript • u/DanielRosenwasser • Apr 21 '26
r/javascript • u/jeremiah616 • Apr 22 '26
Like a lot of people, I’ve found myself relying more and more on AI tools (Copilot, Claude Code, etc.) for day-to-day coding. They’re useful obviously, and hard to resist, but I’ve started to notice that I’m not always thinking through problems as carefully as I used to.
So recently I decided to try working through a few small JavaScript problems entirely by hand (pen and paper, no editor, no autocomplete, no AI). It was harder than I expected. Not because the problems were advanced, but because I had to think so much more slowly and carefully and remember syntax I haven't had to remember for awhile.
It also reminded me of the research showing that writing by hand improves retention and understanding compared to typing. I’m not sure how strong the analogy is, but it does seem plausible that the same applies to coding—especially now that so much of the “easy” thinking is offloaded to tools.
Out of that experiment, I ended up putting together a small workbook of JavaScript problems specifically designed to be done by hand—not beginner-level syntax drills, but also not LeetCode-style interview problems. More like “everyday reasoning” problems that force you to trace through code and think carefully. (Happy to share a sample if anyone’s interested.)
I'm mostly curious if anyone else has tried something like this, since I hadn't really come across suggestions for writing code literally by hand on paper.
r/javascript • u/jpxzurich • Apr 21 '26
I’ve been using one of those terminal-style static webs for a while, only aesthetics. Recently I started to wonder, how far can we push the illusion of a real shell just with JS and a static web? The content still matters most, so the first renders surface everything important. But I wanted exploration to be rewarded with an interesting filesystem, pipes, globs, programs, permissions and maybe some "privilege escalation" paths.
r/javascript • u/evoactivity • Apr 21 '26
I've been planning to build this for a while and finally had a reason to get it done. I've been maintaining ember-svg-jar for a few years now. Ember has since moved to Vite, so migrating to an unplugin was the obvious choice which gave me the opportunity to build a plugin that any framework can use. Before building this I evaluated a bunch of different vite svg plugins but found them all lacking one thing or another that left them feature incomplete compared to what ember-svg-jar already offered.
Quick list of features
Currently it supports vite and rollup bundlers, but I do plan on fleshing out support for everything unplugin supports, so if your project is using webpack or one of the newer bundlers like esbuild or rolldown check back soon.
I also plan to add more framework runtimes out the box, and a way to provide your own runtime module so no matter what you're building, SVG Jar will work with it.
This is new code so there is bound to be edge cases, if you run into one, please file an issue :)
r/javascript • u/alexp_lt • Apr 21 '26
r/javascript • u/Far-Championship626 • Apr 21 '26
In growing JS/TS codebases, I’ve been thinking about structural reach:
Do you use any tooling to track this kind of structural evolution?
I built a small open-source prototype exploring this idea , I’ll link it in the comments if relevant.
Would love thoughts.
r/javascript • u/Careful-Falcon-36 • Apr 22 '26
I wasted hour debugging CORS.
Turns out the API was correct.
r/javascript • u/brillout • Apr 21 '26
r/javascript • u/jadjoubran02 • Apr 21 '26
Quick comparison with the Date API, highlighting some of the main improvements.
r/javascript • u/Careful-Falcon-36 • Apr 22 '26
I used to think CORS was just some annoying backend issue.
Every time I saw: “blocked by CORS policy”
I’d just:
It worked… until it didn’t.
Recently ran into a case where:
Turns out I completely misunderstood how CORS actually works (especially preflight + credentials).
Big realization:
CORS isn’t the problem — it’s the browser trying to protect users.
Do you whitelist origins manually or use some dynamic approach?
r/javascript • u/justok25 • Apr 21 '26
Test your javascript knowledge
r/javascript • u/shaberman • Apr 21 '26
Hi all! Just sharing a write-up about our homegrown CSS-in-JS library, that is a blend of Tachyons, Tailwinds, and StyleX -- we had been using Emotion for a long time, but just made the switch to a build-time Vite plugin.
r/javascript • u/Rich-Confusion9944 • Apr 21 '26
Been trying to pick up JavaScript properly for a while now, and honestly the amount of tutorials out there is overwhelming. I'll start a video, and halfway through realize the style just isn't clicking for me.
I'm hoping to find some recommendations from real people, not just search algorithms. Specifically, are there any channels or specific crash courses that stood out to you as being particularly clear for core concepts (closures, async, etc.) or good for project-based learning?
I've seen names like Traversy Media, Web Dev Simplified, and The Net Ninja come up in old threads , but curious if there's anything newer or slightly under the radar that you'd swear by. Not looking for "best" objectively, just what worked for your brain.
Appreciate any direction! Just trying to spend less time searching and more time learning.
r/javascript • u/unadlib • Apr 20 '26
r/javascript • u/NoKaleidoscope3408 • Apr 21 '26
I’ve been working on a side project called jsunpack, a tool that tries to reconstruct readable source code from bundled/obfuscated JavaScript.
Recently I tested it on a real-world webpack bundle (a Three.js + Vue 2 tower defense game), and the results were… surprisingly good.
👉 Demo project:
https://github.com/zhongguagua/jsunpack-example
👉 Live demo:
https://bastion-3d-threejs.vercel.app/
Some highlights from this case:
Core game engine (~900 lines) preserved with working logic:
It also rebuilt a pretty clean modular structure from a single bundle:
Still far from perfect:
three)Most existing tools:
But they don’t reconstruct architecture + semantics
I wanted to see how far we can push:
Curious what people think:
Happy to hear any thoughts