r/Nuxt • • Nov 27 '25

v4.20: High Performance. Zero Complications.

0 Upvotes

We just updated our Nuxt Starter Kit v4.20 🌿 to the latest:

  • Nuxt 4.2.1

  • Nuxt UI 4.2.1

Built with a clean stack — Nuxt, Nuxt UI, Tailwind v4, Pinia, Nuxt Image, v4.20 are designed to keep your start fast, simple, and complication-free.

Our goal stays the same:

Help you launch Nuxt projects instantly, with a setup that scales from small ideas to full products.

And yes — we finally reached the version it was born to be:

v4.20 🌿

Stay elevated. Build higher.

Demo: https://v420.ecostudios.dev/
Repo: https://github.com/cesswhite/v4.20

EDIT FOR ACLARATION:

Ok guys — a lot of people are calling this useless, and that’s fine.

But here’s the point, straight up:

This starter kit is meant to stay 100% up-to-date with Nuxt and Nuxt UI.

Those two alone let me build almost anything. Add Pinia with SSR hydration, Nuxt Image, a minimal UI setup, a few components for logo/theme/primary color, a tiny store example, and basic SEO — and you have a clean, modern base ready to build on.

Everything here is so you don’t have to set it up manually every time.

Clone → install → remove two small blocks → start coding.

Done.

And yes, you can say, “I can install everything your kit has in 10 minutes.” Exactly, you shouldn’t need 10 minutes to start a project, it should take 1 minute to clone and 1 minute to delete what you don’t need.

That’s the whole point.

I’ve seen starter kits with 10+ dependencies — auth, DB, payments, analytics, AI, storage, etc.

Be honest: no real project starts like that. You start with an idea and a blank canvas.

This kit is that blank canvas, just cleaner.

And about the “420” thing — seriously, it’s just a number.

When this was created, Nuxt 4 and Tailwind v4 didn’t even exist yet. It was just a fun wordplay for the future “4.x” versions.

Now the versions line up and the joke works.

Relax. It’s a template, bro. Just smoke, code, and chill.

If it’s not for you, that’s totally fine.

But calling it useless because it doesn’t ship with 20 features you won’t use on day one… that’s missing the point completely.


r/Nuxt • • Jun 26 '25

Switching to Next js

0 Upvotes

I’ve been a big fan of Nuxt and Vue features like v-model, the reactivity system, and the overall developer experience really won me over. That said, I’ve hit a breaking point recently trying to find a solution for simple things, especially around routing and layouts. Trying to do something seemingly simple like nesting pages and reusing layouts turned into a huge time sink. It took me forever to figure out, and the worst part? The solution wasn’t even in the official docs.

Now, I get it, some might say this is a “skill issue” Fair enough. But honestly, the lack of up-to-date, accessible resources doesn't help. The YouTube scene for Nuxt has been pretty dormant. A lot of the creators who used to cover Nuxt haven’t posted anything in years. CJ from the Syntax podcast is doing solid work teaching Nuxt and Vue, but part of me wonders if it’s sponsored content (even if he doesn't say so). I wouldn't be surprised if he stops soon too.

Everyone talks about how awesome the Vue/Nuxt community is, and don’t get me wrong, there are amazing people and active contributors, but I’ve seen GitHub issues sit unresolved for months or years. Even here or on r/vuejs, questions sometimes just… go unanswered.

I totally get that Nuxt and Vue are open-source projects and don’t have a giant company behind them. But it’s rough when most quality tutorials are locked behind a paywall. Don’t even get me started on UI libraries.

And then there’s VS Code support. It just feels clunky and takes way too much configuration to get things working the way I need.

Anyway, I could go on and on, but that’s why I’m making the switch to Next.js. Anyone else feeling the same frustration? How are you dealing with it?


r/Nuxt • • Jul 30 '25

Because I got millions and billions and trillions of DMs, here's how I use Claude in my repo

0 Upvotes

I posted "I created a boilerplate so you don't have to" a few hours ago and got tons of repo traffic, plus my DMs are flooded with people asking about my agent/* folder setup.

Here's my complete workflow for using Claude Code CLI (I don't use this method constantly, but for smaller tasks, it's my preferred approach):

The Process:

  1. Initial Setup: Open Claude Code CLI and establish context with a friendly greeting

  2. Planning Phase: Switch to plan mode and DISCUSS your problem/feature in detail

  3. Requirement Clarification: When Claude offers to start coding immediately, resist! Keep the conversation going until you're 100% confident she understands both the problem and your desired outcome

  4. PRD Generation: Switch to auto-accept mode and run: @agent/create-prd.mdc please write a PRD for this

  5. PRD Review: Claude creates ./tasks/[project-name]/prd-xyz.md - review and refine as needed

  6. Task Generation: Once your PRD is solid, run: @agent/generate-tasks.mdc I have updated the PRD, please read the update and generate tasks for ./tasks/[project-name]/prd-xyz.md

  7. Task Refinement: Review the generated top-level tasks in ./tasks/[project-name]/tasks-prd-name.mdc, make adjustments, then tell Claude to proceed

  8. Subtask Creation: Claude will break down tasks into subtasks - review and approve

  9. Execution: Launch the workflow with: @agent/process-task-list.mdc let's start with ./tasks/[project-name]/tasks-xyz.md

  10. Monitor & Guide: This is crucial - stay engaged and observe Claude's work. Don't just walk away!

Happy to answer any questions about the setup or share more details about the individual agents!


r/Nuxt • • Jun 16 '25

Wrote a whole Comprehensive Guide on an AI Design System with Nuxt and Nuxt UI

2 Upvotes

I’ve always been a fan of Vue and it’s great what Nuxt has done. I’m designed challenged so I thought maybe I should figure out a way to help with the design process by using AI. I knew I wanted to use Nuxt and Nuxt UI. My whole idea is that I would be able to visually see how my app could look and feel before actually building it out. Industry standard today in the professional world is to have a UI/UX designer create a design system. These typically are made in Figma, but I essentially made one in a live app.

There’s two parts to it:

  • gathering the information about your UI framework that you want to use

  • tailoring my AI design system prompt for your specific needs

Here’s the main prompt but there’s a bunch of steps that help get a much better output. You can adjust pretty much everything just leave the GREAT DESIGN SYSTEM GUIDELINES as-is:


/sequential-thinking /ensure-accuracy

# Design System for web app

## Goal
Create a great design system based on the sections below in GREAT DESIGN SYSTEM GUIDELINES to be used for the intended use. This design system uses [UI framework name] components.

## Intended Use

This design system will be for [short description of what problem your app resolves for its users. You can even describe their emotions.]. It’s target audience [describe the if the target audience is or isn't tech savvy and any other tendencies that would be useful to know].

## Specifics

1  The design system MUST BE a Nuxt web app and not a written document
2  Ensure that you follow the steps for each section in GREAT DESIGN SYSTEM GUIDELINES. This is VERY IMPORTANT.
3  VERY IMPORTANT to ensure you cover all sections in GREAT DESIGN SYSTEM GUIDELINES
4  For micro interactions include things that aren’t just a simple grow animation
5  Show examples of components that could be used in the app using spacing to communicate visual hierarchy. They must be delightful in a UI/UX sense. The components must be related to the app.
6  In the examples of components ensure that use you use visual hierarchy and contrast to draw attention to a specific CTA. DO NOT draw attention to multiple elements at the same time. Avoid confusing the user.
7  Show examples of deliberately breaking UI design guidelines in order to bring visual interest and attention. Ensure you show at least 4 examples.
8  Create 4 different themes of color palette/typography combinations that I could dynamically switch to so that I could see what I like the best.
9  Avoid serif fonts. Try fonts that aren’t commonly used but are visually appealing.
10 Create a variety of rounded sizes and no rounded corners that I could dynamically switch to to see what I like best.

# GREAT DESIGN SYSTEM GUIDELINES

1  Typography: A clear hierarchy of fonts, sizes, weights, and styles to ensure readability and visual consistency across headings, body text, and other typographic elements.
2  Color Palette: A defined set of primary, secondary, and accent colors, including shades and tints, with guidelines for usage to maintain a cohesive look and ensure accessibility (e.g., contrast ratios).
3  Layout and Spacing: Standardized spacing units, grid systems, and layout patterns to guide the arrangement of elements, ensuring alignment, balance, and responsiveness across different screen sizes.
4  Iconography: A consistent set of icons with unified style, size, and weight, designed to communicate actions or concepts clearly and align with the app’s aesthetic.
5  Imagery Guidelines: Rules for using images, illustrations, or other visual assets, including style, tone, and proportions, to maintain a unified visual language.
6  Components: A library of reusable UI elements like buttons, inputs, cards, modals, and navigation bars, with defined styles, states (e.g., hover, disabled), and variations to ensure consistency.
7  Patterns: Common design solutions for recurring needs, such as forms, tables, or search interfaces, with guidelines for their application to streamline user interactions.
8  Tone and Voice: A defined writing style for text in the UI, including labels, error messages, and tooltips, to ensure clarity and alignment with the app’s personality.
9  Accessibility Standards: Guidelines for inclusive design, such as color contrast, keyboard navigation, and screen reader compatibility, to make the app usable for all.
10 Motion and Animation: Principles for transitions, micro-interactions, and loading states to enhance usability and engagement without overwhelming the user.
11 Do’s and Don’ts: Provide visual examples of correct and incorrect usage. For example, “Do: Use primary blue for main buttons. Don’t: Mix multiple button styles on one screen.”
12 Contextual Guidance: Show how elements adapt to different contexts, like a button shrinking slightly on mobile but retaining its core style.
13 Contrast and Focus: Provide guidelines for using contrast to draw attention (e.g., a red “Buy Now” button against a white background). Include accessibility notes, like ensuring a 4.5:1 contrast ratio for text.

These elements work together to create a cohesive, user-friendly, and visually appealing experience while maintaining consistency across the web app.

r/Nuxt • • Jul 27 '26

I’m building NuxtAdmin, a full-stack Nuxt admin system with Codex

Thumbnail
reddit.com
24 Upvotes

r/Nuxt • • Mar 16 '21

Discussion Why does the Nuxt.js docs suck so immensely?

11 Upvotes

I understand Nuxt is free so there's just no basis to complain - also if I'm unhappy I should fix the issue myself instead of ranting (I can't, I just don't have the technical level).

I guess I'm simply curious: how can a successful framework go on for years without anyone at anytime even thinking of doing something about its terribly poor documentation? It would take one guy working on it for a few weeks to solve this tremendous issue.

I wanted to understand isDev/isClient/isServer: what, how, when, etc. Well, documentation answers none of these questions.

Same thing with publicRuntimeConfig and privateRuntimeConfig: no examples, no explanation beyond the briefest description possible.

I'm sure these things are obvious for `Nuxt` contributors & advanced devs but millions of us are not so advanced and need explanations.

Those are random examples but Nuxt.js's docs in general are just incredibly unhelpful. It's ironic because Nuxt is based on Vue, whose docs are exemplary.

Guys please do something about it, end the suffering.


r/Nuxt • • Dec 11 '21

Discussion Nuxt is stupid. There is no support and community behind it. [Change my mind]

4 Upvotes

I love vue but I am changing it for Next js.

I wish nuxt has more active community

The issues in nuxt project are stagnant for months. Nobody responds to the github issues.

Hotreload does not work and takes so much time. Debuggins is so hard.

No opensource project and tutorials for things you have to figure out all the things while Next js has so much community support and have really good opensource projects.


r/Nuxt • • Jun 16 '21

Jobs Hiring Jr to Mid level VueJS developers. (Worldwide) (Full Time) (Part Time)

Thumbnail
laser.gg
0 Upvotes

r/Nuxt • • Dec 07 '24

I built a Nuxt SaaS boilerplate and you get the entire website's source code

3 Upvotes

Hi Nuxt community! I've spent the last few months building a production-ready SaaS boilerplate, and I wanted to share it here. The best part is that you get the complete source code of saas-boilerplate.dev – meaning you start with a fully working SaaS including:

Everything that's already built:

  • Complete auth system with team management

  • Enterprise-grade role-based access control

  • Working payments (Stripe/Paddle)

  • Email system (works with any provider)

  • Landing page you see now

  • Blog & docs sections

  • Deploy anywhere (AWS/Vercel/Cloudflare/Hetzner)

It's all built with end-to-end TypeScript and tRPC. You can create an account to try every feature live.

I'm offering early access for $99 (regular price will be $149) with lifetime updates and access to our Discord community.

I'd be happy to answer any questions about the technical details or features.


r/Nuxt • • Sep 18 '25

Nuxt 4 folder structure

0 Upvotes

The biggest visible change is how projects are organized. Your application code now lives in an app/ directory by default: https://nuxt.com/blog/v4


r/Nuxt • • May 15 '25

Facing real-world coding and AI challenges building my SaaS (ep2 dev log)

Thumbnail
youtu.be
0 Upvotes

Hey there!

Aleksa here, continuing my build-in-public challenge as a 16yo "entrepreneur" (I don't sell anything for now).

While AI tools offer incredible potential, episode 2 was a deep dive into the reality that they don't eliminate the need for understanding, planning, and debugging.

I tackled implementing core features like authentication (integrating with Supabase) and structuring the project to work effectively with AI code generation (using Cursor). Ran into unexpected errors, folder structure issues, and spent a good chunk of time troubleshooting and learning how to give AI the right guidance.

The video shows the practical side of debugging and problem-solving with a modern stack (Nuxt, Supabase, AI) and highlights that even with powerful tools, the developer's role in understanding and directing the process is crucial.

If you're interested in the technical nitty-gritty of building a real application and working with AI code assistants, check out the latest dev log.

Hope you find some value inside and eventually embark on a similar journey!


r/Nuxt • • Sep 25 '23

Nuxt 3 development too slow, nothing works and eventually will be the death of Vue NSFW Spoiler

30 Upvotes

WARNING - UNPOPULAR OPINION

Firstly, thanks for all the hard work... kind of. Open source projects are great, but they also suck when they don't get enough financial backing. This is currently the problem with Nuxt 3. Each release introduces a regression or new bugs and every time I upgrade my app, it's like a Russian roulette - will the build succeed or will it all light up like a Christmas tree? And guess what - it's usually the latter.

Nuxt 3 is NOT PRODUCTION READY. Claiming so is misleading and will eventually be the nail in the coffin on what used to be a great framework. You cannot tell people it's ready to be used, if each week there's issues (bugs) being raised on GitHub. In fact, there are quite a few issues that still pending reproduction or investigation... maybe they will be fixed in Nuxt 4? Who knows? Such a shame that the lovely workhorse framework we had (Nuxt 2) is being killed off in favour of this lump of random features called Nuxt 3.

The team is too focused on meaningless features like shaving 0.000000000000001 ms from Nitro response times, whereas in reality it does not matter, because NITRO IS TOO SLOW ANYWAY. And the documentation sucks big time. And most of the plugins are incompatible or completely deprecated.

Vue i18n? Don't even get me started. Another great plugin which has been rendered completely useless with the introduction of Nuxt 3. Nothing works, accessing translations in SSR is a pain and needs a workaround, pretty much everything throws some kind of errors all the time.

This seems to be the case with pretty much every plugin or extension, or Nuxt itself. Another release, another bug. And nobody knows why it's happening or how to fix it, the team is too busy focusing on creating Vue Mastery courses (I get it, they want to cash in while they still can) and announcing new minor meaningless features rather than fixing existing bugs.

It's such a shame, because Vue and Nuxt have truly been a fantastic alternative to Next.js, but I can no longer recommend it. I find myself fighting the framework just way too much for it to be dependable.

Guys, if you're reading this - PLEASE, TAKE A STEP BACK AND COME UP WITH A PLAN.

We don't need new features - we need STABLE features, things that work. Where is nuxtServerInit, huh? So many people have gotten used to it - make it happen for Nuxt 3!

Anyway, I digress.

Core Nuxt maintenance team needs more funding, or more people and better project management.

Nuxt 3 is unreliable, ridden with bugs and the project status is questionable - I would personally NEVER recommend Nuxt 3 to anyone.


r/Nuxt • • Jul 20 '21

The MasteringNuxt course is now complete! Join now and get 40% off!

Thumbnail
masteringnuxt.com
2 Upvotes

r/Nuxt • • Aug 15 '26

Serverless Bill Shock: Tracking Edge Function and Database Expirations (Vercel, Supabase, Netlify, Neon)

3 Upvotes

For over two decades, agency hosting economics were beautifully predictable. You bought a reseller web server or dedicated cPanel account for $50 a month, crammed 30 client WordPress sites onto it, and charged each client a flat $25 monthly maintenance fee. Your margins were clear, your server bills were static, and billing surprises were virtually non-existent. Read the comple te article here > Serverless Bill Shock: Track Vercel & Supabase Client Costs | InstaRenewal

Then came the modern web stack.

Driven by the demand for lightning-fast digital experiences, agencies aggressively migrated to decoupled architectures: Next.js, Nuxt, Vercel, Supabase, Cloudflare Workers, and serverless databases like Neon. While the performance gains of this modern paradigm are undeniable, it introduced a chaotic operational reality: micro-subscription fragmentation and variable utility billing.


r/Nuxt • • Jul 30 '20

Nuxt Fingerptint

Thumbnail
github.com
0 Upvotes

r/Nuxt • • Feb 05 '24

What are really want to this community...

0 Upvotes

I rely dont like react and next almost hate but I use but they have bigger community from vue and nuxt. Im on youtube and I like and enjoy to watch videos about "tuts" about how to build clones of trello, youtube, facebook, saas, ai, banks, whatever, etc all of these kind of projects. All of these videos is about react/next less than 1% is nuxt. I hope nuxt community to have more people to create youtube videos.


r/Nuxt • • Jun 15 '24

Nuxt vs Nitro

1 Upvotes

Is Nuxt just serving as the frontend, and Nitro severving as the backend. Asking because I am not seeing anyting like an option to make a page or component serverside or client side like it is done in Next Js with " use client " ). If what I proposed is correct, does that mean I need to learn Nitro before I cannot be good at using the server folder in Nuxt?


r/Nuxt • • Oct 12 '26

Building real-time AI workflows with Nuxt and Discord on a budget VPS

1 Upvotes

One thing I focused on while designing real-time AI workflows was keeping the infrastructure simple and affordable during the early days.
Nuxt handles the dashboard and API routes, while a Discord bot delivers notifications. For live updates, SSE is often enough without the extra complexity of WebSockets.
For background jobs and event handling, Redis can act as a lightweight queue. Important events are persisted in PostgreSQL for historical playback, while the dashboard fetches older events through an API and streams new ones in real time.
The idea is to start with a single VPS, avoid introducing RabbitMQ or multiple separate services too early, and keep the architecture ready to scale when traffic actually demands it. Database writes can be batched, and queue consumers can apply backpressure when the database is under load.
I’d rather optimize the resource usage of a small deployment first than pay for infrastructure designed for traffic I don’t have yet.
How are others balancing real-time features and infrastructure costs when launching a new product?


r/Nuxt • • Jun 01 '26

MagicSync Open source not just a simple social media management tool

0 Upvotes

MagicSync Open source not just a simple social media management tool

I have been working on and off in MagicSync for the last couple of months in my free time, for one side i wanted to learn more about nuxt and specifically:

  1. Nuxt layers

  2. Nuxt tasks

  3. Nuxt monorepo

  4. Nuxt UI

  5. Transformersjs

  6. MediaBunny

  7. fabricjs

  8. Better Auth

Github

Documentation

Live site Not open to the public to test I use it my self 😃

What it is ?

**An alternative to: Buffer.com, Hypefury, Twitter Hunter, Postiz,etc...

**MagicSync helps you manage your social media posts,
build,capture leads, grow your business and the most important point is: Save time.

packages/
├── db/          # Database layer (Drizzle ORM, Turso)
├── auth/        # Authentication (Better Auth)
├── assets/      # Media upload & management
├── scheduler/   # Post scheduling & calendar
├── connect/     # Social platform connections
├── tools/       # In-browser tools (image editor, etc.)
├── ai-tools/    # AI content generation
├── bulk-scheduler/  # Bulk post creation & scheduling
├── content/     # Static content & blog
├── ui/          # Base UI components (@nuxt/ui wrappers)
├── email/       # Email templates & service
├── site/        # Main application (layer merge point)

Unique offers :

  1. You can create Environment variables (private \ public) that you can use - When creating a social media post - AI Chat - When creating bulk social media post

Example of use case:

When creating a social media post/video for you want to add the information of a restaurant but you don’t want to manually type the

  • name

  • email

  • number

  • direction

  • hours

  1. create variable with all the information

  2. Create the post and click on the variable that you want to add at the end

  3. Import from CSVImport content that you have planed from somewhere else or that your team have in some sheet export it to csv and import it to the platform and it will be scheduled base on the schedule time

csv columns

1.Content(required) 2.image_url → will download the image to the system 3.scheduled_time 4.Comments - > array of strings that can be added to the post as commends

Spread the post for specific timeframe and select specific accounts to port it to.

3. Bulk generate → specific use case was related to restaurant menu with different special every day.

4. Content repurpose

Give it a url it will pull the content and will rewrite the post base on the selected
1. tone
2. platforms
or provide you original post and it will use the tone and platform that you selected

5. Respond to comment for a specific post 6. Free tools 1. Text behind image 2. audio transcription 3. audio player 4. Image editor 5. video silence remover 6. podcast explorer and player

This is a free tool, I dont make money from it, I was planing to host it and offer it to others but currently, i dont have the time for it

Self host is recommended with coolify with a docker container

ghcr.io/leamsigc/magicsync


r/Nuxt • • Apr 26 '25

A GUI for generating images locally with the new OpenAI gpt-image-1 APIs

0 Upvotes

I gave myself 3 minutes to search for an open-source project to generate images with OpenAI's APIs locally using Nuxt, but I found nothing, so I made one myself in "3 minutes." Do you like it? I gladly welcome contributions.

Github: https://github.com/Teygeta/nuxt-gpt-image-1


r/Nuxt • • Jan 25 '22

Tutorial Building An E-commerce Store with Nuxt.js and Strapi

0 Upvotes

r/Nuxt • • Jun 22 '24

Tired of Svelte I would like to know if there is an easy way to do this in Nuxt/Vue

0 Upvotes

I'm a backend programmer and usually when I need to do something simple on the frontend I used Svelte and Svelte Kit.

But in these last few days I have to do something more complicated than usual and I realized something incredible: if I understand correctly, there is no library or code already written and battle tested that allows you to save variables and to replace them when changing the URL with the "back" and "next" buttons.

I opened various questions in the "Discussions" section of Svelte Kit and Svelte Github repos and in Discord but either I didn't receive answers or they answered me without a practical solution.

I really regret this and I think this is the lack of community and libraries and real code examples when they don't recommend Svelte instead of Vue or React.

So the question for you, Vue/Nuxt people:

Is there a SIMPLE way in Nuxt to persist in the URL the filter conditions of a dashboard or a list so that I can:

  1. return to previous filter settings when I go back and to subsequent ones when I go forward with the browser keys or

  2. save those filters (javascript simple objects with `JSON.stringify()`) in the browser bookmarks or as a link to share with some people?

I don't need browser DB, special cache levels, localStorage, none of this.

In Svelte Kit I wrote some code a few hours ago that works, but since I'm not good at javascript nor Svelte I don't know how to make it a universal helper for all pages.

And among other things, I don't want to re-invent a new (surely punctured) wheel.

That's why frameworks exist, right?

UPDATE:

I updated the question to be more specific about my needs.


r/Nuxt • • Mar 12 '26

Senior Full-Stack engineer @Qleer.ai

0 Upvotes

Freelance · Full-remote · Potential long-term role

About Qleer

Qleer.ai builds AI-native solutions to automate complex regulatory and normative compliance analysis. We turn dense, unstructured legal and technical data into strictly verifiable, zero-hallucination compliance decisions.

The Role

We are looking for a senior full-stack engineer to join us on a freelance basis, with a clear path toward a long-term core engineering position.

This is not a ticket-execution role. You will work directly with the technical founder, take meaningful ownership of features, and have a real influence on the platform's architecture and direction.

Stack

Frontend: Nuxt 4, Nuxt UI, Tailwind CSS. Backend: Nitro server routes (TypeScript). Database: Supabase (PostgreSQL, RLS, migrations, branches). Cloud: GCP (Vertex AI, Cloud Run, Storage). Hosting: Vercel.

What We Look For

Required

  • Strong experience with Nuxt (3/4) and the Vue 3 ecosystem (Nuxt UI, Vueuse)

  • Solid foundation in Supabase, SQL modelling, RLS, migrations, branches

  • Clean, maintainable TypeScript, architecture that stands the test of time

  • Ability to own and deliver complete features end-to-end

  • Autonomous, reliable, and communicates clearly

Nice to have

  • Experience with AI pipelines or LLM integrations

  • Background in B2B SaaS or compliance/regulatory tooling

  • Familiarity with Vertex AI or Google Cloud

How We Work

  • Async-first: no unnecessary meetings, results over presence

  • Small team, fast iteration: decisions are made quickly

  • Ownership mindset: features are yours from design to production

  • Open-source discipline: clarity, documentation, modularity

Practical Details

Start: As soon as possible. Location: Remote (European time zones preferred). Availability: 3–5 days/week. Contract: Freelance, with paid initial milestone. Evolution: Long-term position for the right person.

Send your application to [email protected]


r/Nuxt • • Apr 01 '25

Sharing my ultimate tech stack in 2025

12 Upvotes
  • Framework (Nuxt.js)

  • UI (TailwindCSS + NuxtUI + OriginUI-vue)

  • Database (Sqlite + Drizzle ORM)

  • Email (Resend)

  • Payment (Stripe)

  • Analytics (Umami)

  • Deploy (NuxtHub)

I think this tech stack has great DX and low running costs, making it perfect for indie hackers.

Plus, it doesn’t have the recent security issues that showed up in Next.js.🤔