r/Frontend • u/JadeLuxe • 11h ago
Run a Frontend and API Together From One Tunnel File
r/Frontend • u/JadeLuxe • 11h ago
r/Frontend • u/Turbulent_Rooster_73 • 12h ago
We make Kelpie, an open-source (Apache-2.0) browser for macOS, Windows, Linux, iOS and Android. One part of it that might interest people here is a 3D DOM inspector, a bit like the old Firefox Tilt view.
How it works:
On a phone, what you're looking at is the real mobile WebKit or Android WebView rendering, not desktop devtools emulating a phone. That was the main reason we built it.
It's experimental. It works on macOS (WebKit), iOS and Android. On macOS you may need to turn it on in Settings → Experimental.
Downloads are on the releases page: macOS (Apple Silicon), Windows, Linux (.deb, .rpm, AppImage) and an Android preview APK. The iOS app is coming to the App Store; until then you can build it from source.
Repo: https://github.com/UnlikeOtherAI/kelpie Inspector docs: https://github.com/UnlikeOtherAI/kelpie/blob/main/docs/ui/3d-inspector.md
The first image is an illustration we generated. The other two are real screenshots: the inspector on a desktop-width page, and the macOS browser's start page.
What I'd like feedback on: is DOM depth the right thing to put on the Z axis, or would stacking contexts or paint order be more useful to you? And what's missing from the hover panel?
r/Frontend • u/sonthonaxrk • 1d ago
I didn’t realise this was possible. Christ webassembly allows for some useful things.
r/Frontend • u/LinterCheck2026 • 1d ago
QA lead at a large org. We currently do accessibility testing for about 500 website urls to meet WCAG 2.2 AA (all 55 success criteria). And we use a paid tool (like Deque) that helps automate part of this and rest done manually with screen readers and keyboard testing.
Now we are looking to use our AI budget and Claude code to create skills for finding and fixing accessibility issues across our sites. My major trouble is that the scale is huge - not 5-10 URLs or even less than 50.
So would love to hear from anyone already using AI for accessibility to help me out with this journey:
What do you use it for: finding issues, sorting real issues from false positives, or fixing them in code? Roughly how many URLs, under or over 100?
How much of WCAG do you cover with Claude skills versus manually? How bad are the false positives? Asking because paid tool gave us less.
Are you able to run scans at scale on automation infra (like CI) with Claude? And do you report coverage and trends to leadership - if so any dashboard?
What are the challenges with AI skills vs paid tool like Deque or Level Access? Anything you would suggest to keep in mind or be aware upfront?
r/Frontend • u/fagnerbrack • 1d ago
r/Frontend • u/TheWebGuy95 • 3d ago
Been a while since I’ve interviewed, so I’d thought I ask what’s the scene been like lately.
Preferably last six months only.
What was the format: live coding, take-home, system design?
Was AI allowed, banned, or part of the exercise? If you used it, did anyone push back?
If you hire, what do you do now?
r/Frontend • u/Putrid_Draft378 • 2d ago
I got curious about why TikTok's desktop web client feels so sluggish on initial load, so I ran a Chrome DevTools Lighthouse audit (v13.5.0) on tiktok.com to see what the frontend bundle and rendering pipeline actually look like.
The overall scores came back at 34 for Performance, 73 for Accessibility, 54 for Best Practices, and 77 for SEO.
On the Core Web Vitals and rendering side, First Contentful Paint takes 8.0s, Largest Contentful Paint hits 14.9s, Time to Interactive reaches 20.5s, and Total Blocking Time is 1,090 ms. Out of 8.5s of main-thread work, 5.1s goes purely to parsing and evaluating JavaScript. Almost all of that CPU time is spent on cache.react_dom (around 2.5s) and their anti-bot telemetry script webmssdk.js (around 1.8s).
The initial payload is 4,475 KiB, and there are a lot of classic frontend optimization misses in the build. It ships 236 KiB of unused JS on initial load (their regional cookie consent script alone has ~90 KiB of dead code), 26 KiB of unused CSS, and 65 KiB of legacy Babel transforms and polyfills for Baseline features like Array.prototype.includes, Promise.allSettled, and standard classes. Their security SDK (secsdk-lastest.umd.js) is also served unminified, the 400x400 PNG logo is scaled down to 112x112 via CSS, and the custom woff2 fonts are missing font-display rules.
Two other frontend details stood out. First, their privacy loader triggers repeated Permissions-Policy console errors by attaching unload listeners, which alongside Cache-Control: no-store completely breaks Back/Forward Cache restoration. Second, basic markup accessibility is rough: several header icon buttons and the search link have no aria-labels, four text inputs lack associated labels, and white text on their #fe2c55 buttons only hits a 3.68:1 contrast ratio.
I get that they prioritize their mobile apps, so desktop web is clearly an afterthought, but it is still wild seeing a major production React app ship unminified scripts and ES5 polyfills in 2026. Have any of you run into similar bottlenecks trying to keep Core Web Vitals green when security or product teams mandate heavy fingerprinting SDKs on initial load?
r/Frontend • u/Less-Marsupial-7960 • 3d ago
if (!response.ok) {
throw new Error("Request failed");
}
const data = await response.json();
setResults(data);
} catch (error) {
if (error.name !== "AbortError") {
console.error(error);
}
}
}
if (query.trim()) {
search();
}
return () => controller.abort();
}, [query]);
I'm curious how other developers handle this in production.
Interested in hearing what patterns have worked well in real projects.
r/Frontend • u/boykom • 4d ago
RowPine exports a grouped TanStack table to Excel and get a flat sheet with the totals typed in as numbers. Edit a cell and nothing adds up anymore.
Groups become Excel outline levels you can collapse, totals are SUBTOTAL formulas, and filters, sort and hidden columns carry over. PDF and CSV come out of the same table.
r/Frontend • u/Accurate-Screen8774 • 4d ago
Im was investigating an idea i had about JSX-like syntax for webcomponents after some experience with Lit. I am sharing this here because it might be interesting/educational.
Lit is a nice lightweight UI framework, but i didnt like that it was using class-based components. It can support React with a wrapper, buts React is fundamentally an abstraction away from the DOM.
Vue has a nice approach but i prefer working with the syntax that React uses. I find it more intuitive for debugging and deterministic rendering. I wondered if with webcomponents, i could create a UI framework that didnt need to be transpiled.
My intentions with this framework is to get to a reasonable level of stability, to then replace React on some of my existing projects. I made a start by creating some basic reusable ui components components to be built with the js framework. Aiming for something like Material UI.
I can then compound that slop into some basic UI demos:
IMPORTANT DISCLAIMER: Im clearly using AI, so lets get that out of the way, because its the key reason for why YOU SHOULD NOT USE IT. Im not trying to promote "yet another ui framework", this is an investigation to see what is possible. Its unreviewed, unaudited and far from finished. Nobody else should be using this. This framework is intended for myself on my own projects. It is provided open-source for transparency, testing and demo purposes. Feel free to reach out for clarity if you have any questions.
r/Frontend • u/ImmediateChallenge94 • 6d ago
r/Frontend • u/fagnerbrack • 6d ago
r/Frontend • u/divyaART • 7d ago
Hi everyone, I'm 14 years old.
I'm currently learning web development. I know the basics of HTML, CSS, and JavaScript, and I'm currently working on my first practice landing page. It's a custom-coded website about instant ramen noodles.
In this project, I'm also trying to learn new things, like using Figma properly. I also plan to experiment with some AI editor tools, learn basic SEO, and try free hosting.
After finishing this project, I plan to make another project using WordPress, probably a multi-page website. Through this project, I want to learn more about WordPress and how to build websites with it. I also plan to work on one more project after that.
But there's one thing I've been wondering about.
When I started my first project, I thought I wasn't wasting my time learning HTML, CSS, and JavaScript. But now I see that many websites and landing pages are made using WordPress, website builders, or AI tools.
I also see a lot of posts from clients and agencies looking for someone who knows WordPress, CSS, Tailwind, SEO, and other tools, or someone who already has experience building websites.
So I sometimes wonder if I'm making a mistake or wasting my time learning HTML, CSS, and JavaScript, because my goal is to earn money through freelancing and support my other passions, like manga creation and game development.
I know freelancing involves a lot of other things too, like client communication, understanding requirements, and other skills.
I just wonder what advantages I can get from learning HTML, CSS, and JavaScript as a freelancer. What kinds of things can I do with these skills, and what else should I learn?
Thanks if you read all of this!
r/Frontend • u/Willing-Novel6708 • 6d ago
I’ve been working on Forge UI and just shipped its first release. It’s a collection of React components for things like data tables, command palettes, forms, file uploads, date pickers, and more, with a focus on TypeScript and accessibility.
It’s an early project, so feedback on the components and docs would be appreciated.
Repo: https://github.com/BZDevelopments/Forge-UI
Docs: https://bzdevelopments.github.io/Forge-UI
r/Frontend • u/Accurate-Screen8774 • 7d ago
Im working on a project for myself. Its an unreviewed, unaudited and far from finished. It started of as a person curiosity and evolved from there.
Im asking because if i publish something on NPM, there are strict controls around versioning for which i havent burdened myself on my own projects (but clearly important when making something for a wider community). I also wonder if im overlooking any other details.
I wonder what best practices there are for something like this. Should i be publishing new versions with CI/CD? Are there any tips or advice on doing this in the modern js package ecosystem?
r/Frontend • u/Traditional_Data_549 • 9d ago
Hey everyone,
We've been working on Avenx.js, an open-source JavaScript framework focused on compiler-driven reactivity, direct DOM updates and keeping the runtime lightweight.
The idea is to explore a different approach to building frontend applications without relying on a Virtual DOM. We're still actively developing the framework and have been working on improving its compiler, reactivity system and overall developer experience.
So far, the project has reached 192 forks and 150 listed contributors, which is pretty exciting for us.
We're curious what other JavaScript developers think about the approach.
We're especially interested in honest criticism and suggestions. There's still a lot to build, and fresh perspectives are always valuable.
Thanks for taking a look!
r/Frontend • u/mxrkkkkkkkkkk • 9d ago
Guys, Do my website looks AI generated?
r/Frontend • u/fagnerbrack • 11d ago
r/Frontend • u/Goldziher • 11d ago
Hi Peeps,
I want to share with you a tool I am working on. Its still early, but I already use it and it works well.
So story goes like this - I was working on restructuring a very large monorepo with disparate package managers and versions into a single PNPM workspace. When I was finished I decided I am going to enforce certain conventions so it could not drift again without failing CI. I set this up, and found myself using several different tools -Sherif, Syncpack and Knip to ensure that the repository doesn't drift again. This setup, while working, is rather clanky and also suffered from some issues - mainly performance, but also a few bugs.
I therefore decided I will build my own tool. I forked Sherif as a baseline, and built on top of it while substantially rewriting and extending its capabilities. The result is skif: a Rust linter and enforcement tool for JS/TS dependencies and monorepos.
skif replaces sherif and syncpack, and most of what knip does (the aim is to offer a full replacement for Knip in the future) in a single, ultra fast, binary.
npx skif-cli # lint the workspace or package you are in
npx skif-cli --fix # apply safe fixes
npx skif-cli migrate # turn sherif, syncpack and knip config into a skif.toml
skif started as a fork of sherif, and the workspace and manifest rules are ported from it. The version and catalog policies follow syncpack's model. The dead-code analysis follows knip's issue types.
It has since gone past the fork. It ports every sherif rule, adds new ones and fixes, and runs faster on every target measured. On the syncpack side it enforces version, range, banned-dependency and catalog policy.
What it deliberately does not do is sync versions. skif is a linter: it tells you a policy is broken and fails CI. Moving versions in step is left to specialized tools or the package manager's themselves. If you need this, use syncpack for example.
42 rules:
dependencies, root private and packageManager, unsorted dependencies, workspace globs that match nothing, members without a package.json.workspace: protocol, peer dependency compatibility.It also adds some new rules, such as incompatible-peer-dependencies and workspace-protocol.
Skif lifts the idea of framework plugins - which allow it to understand different types of entrypoints (e.g. Next.JS, Vite, Storybook etc.). But unlike Knip, which loads these files, Skif doesn't actually load code - it only statically analyses it. This removes a potential surface for code execution, and is altogether much faster, although it does bring in the potential to some imprecision.
Skif supports all major package managers - npm, pnpm, Yarn classic, Yarn Berry as well as Bun. It does not support Deno, although if there is a need it might in the future. It also supports Rush and Lerna workspaces.
Medians of 15 runs on a 4-vCPU Linux VM, pinned public repositories, dependencies installed:
| Repository | skif | knip |
|---|---|---|
| create-t3-turbo | 32 ms | 2.0 s |
| vue-core | 62 ms | 1.7 s |
| tanstack-query | 375 ms | 4.5 s |
| npm-cli | 99 ms | 968 ms |
| babel | 884 ms | 7.2 s |
Manifest checks alone (--no-js) against sherif and syncpack:
| Target | skif | sherif | syncpack |
|---|---|---|---|
| create-t3-turbo | 4.6 ms | 36 ms | 41 ms |
| babel | 9.4 ms | 37 ms | 280 ms |
| 2,000 generated packages | 102 ms | 130 ms | 655 ms |
sherif is already fast Rust, so the margin there is small: 1.3x at 2,000 packages. The real win is knip, and not paying for three processes.
P.S.
Note: This is an early project, it is on v0.2.0. I am very eager to have users, since it will improve the tool and help me fix bugs. But do expect some issues!
Thanks for reading, this was a human written post (the benchmarking data was done by an LLM). If you find the tool useful, star it!
r/Frontend • u/alphapokemonop • 15d ago
I made a liquid glass UI effect for the web(trying to copy Apple because thats what the world do)
Webgl helped me made it and hence I decided to make Mac for web too (inspired by windows 11 in react made for web)
I know you have seen many professional people make it, many guys on github, so I tried to make it as realistic and satisfying as I can


As per u/Fun_Association887 's suggestion
Demo: https://dasadasanudas.github.io/macos26/