Very cool. I do have a couple of questions tho:
1. You mention "Unaffected by AI intelligence" - how does that work?
2. How does it identify and block bots?
Hello all, I built a drag & drop tailwindcss website builder for makes and engineers.
In UiBun you can:
1. Drag & drop pre-made BunUI template blocks
2. Import your own HTML/tailwind code blocks (including TailwindUI and other UI kits)
3. Export production-ready HTML code (Download zip)
Pre-selling SaaS is sometimes frowned upon by the consumers, but the adrenaline boost it gives to us makers is beyond anything else. I just made the first sale for my side project and I am overwhelmed with happyness. Hence wrote a blog post in an attempt to motivate more makers from pre-selling their upcoming products.
I noticed that designers spend almost the same time and efforts developers put to design a webpage. And, developers pretty much rebuild the same design which was created by designers in figma.
I wanted to eradicate this redundancy hence started working on a visual editor that exports code.
Hello all, I built a service called as PrivJs Safe to protect from vulnerable and malicious npm packages. I built it mainly for myself and ended up creating a service out of it. What do you think?
Yes. I have tried this in multiple production apps (including legacy monoliths). As a result, the team was able to identify and fix about 1000 vulnerabilities in the projects.
$npm audit usually warns the developers at install time and is often ignored. Having an ESLint plugin gives active warnings related to the issues and also blocks pipelines wherever necessary.
More than blocking pipelines, This plugin doesn't throw errors for an entire package if only certain methods are vulnerable. For example, in `lodash` only 3 methods are vulnerable. So, it would be wrong to flag the entire package as vulnerable, instead only throw errors if the vulnerable methods are imported/used.
That's why my ESLint plugin comes into picture and feels much better than many other tools available
I created an ESLint plugin to warn developers when they import vulnerable dependencies in a project. It is smart enough to detect vulnerable methods rather than flagging entire import. For example, if only a few methods in a library are vulnerable, the ESLint plugin only throws an error if these methods are imported. What do you think about this?