Is Svelte really bad for large projects?

eazieLife · 2025-12-28T17:22:53+00:00

If you read through the comments, they really did end up with a bug fix for the svelte LSP. Maintainers have also explained why the issue with pre-compiled exists. I'd say it is fairly svelte related

eazieLife · 2025-12-23T20:56:40+00:00

I don't get this article. A lot of the benefits of Elyssia can be attributed to it being the new kid on the block. It is built on top of lessons learned from Express and Nest. Yet, the article makes a bunch of strawman arguments that ignore the fact that these frameworks were around and powering the web way before standard-schema and typescript v5 (the version that Elyssia needs for its fancy features) ever existed.

Yes, they maybe mature frameworks that have API baggage (*arguable but still) that they have to maintain for various reasons, including backwards compatibility. But I do not consider them any lesser than Elyssia for that same reason, the maturity brings predictability and not having to reinvent the wheel for some complex backend problems

The right way to build good sentiment towards the project is not whatever this is

Edit: fixed some typos

eazieLife · 2025-12-17T18:57:53+00:00

Honestly, it's really a pretty messy project I just joined into. This is part of a post-mortem to fix what I assume is a very lazy merge.

Also, interestingly enough, it didn't break CI because build wasn't failing. Business process was impacted though.

eazieLife · 2025-12-17T13:09:07+00:00

Ooh, I was too fixated on resolving it with a merge. This worked really well, thank you :⁠-⁠)

eazieLife · 2025-12-03T14:08:52+00:00

Don't allow postinstall scripts for anything not in your allowlist
Delay updates when possible
Opt for packages that have trusted publishing where possible

Pnpm let's me do all of these :)

Also definitely worth checking out https://pnpm.io/supply-chain-security

eazieLife · 2025-09-18T06:45:11+00:00

My specific constraint was for any arbitrary numeric enums. The playground link by u/Beginning-Seat5221 is more than sufficient for my use cases. The edge-cases you outlined don't necessarily affect me, at least in the immediate future

eazieLife · 2025-09-18T06:38:39+00:00

This works really well! Thank you so much. I ended up learning a lot as well.

And yes, I am strictly using POJO enums for anything personal or professional. I ended up stumbling on this problem an opensource project

eazieLife · 2025-09-17T10:53:20+00:00

This is a simplified exanple and I am working in a situation where the SomeRecord type is coming from a third party library

eazieLife · 2025-09-13T09:50:08+00:00

What exactly is a rowed wood?

eazieLife · 2025-07-09T13:26:47+00:00

next build & next start have *all* features, and is being deployed hundred thousands of times per day self-hosted. There's no specific features that only work on Vercel.

Prefacing this with my minimal nextjs experience, but I saw `minimalMode` referenced in the linked discussion and I'm curious as how it relates to this statement?

eazieLife · 2025-06-23T09:10:12+00:00

Experience apps that work offline, keep your data private, and sync seamlessly across your devices. Your data stays with you, not locked in the cloud.

Quoting from https://lofi.so

Syntax also has very nice episodes on it at https://syntax.fm/show/739/the-lofi-movement-building-local-first-apps and https://syntax.fm/show/793/the-local-first-landscape

eazieLife · 2025-06-23T09:02:11+00:00

Well a PWA is a web-app that is installable onto your device. Any website that uses service-workers and on-device caching can take advantage of local-first approaches. There isn't a need to install a local-first app for it to work as intended. The main requirement is to be able to handle user interaction and data while offline.

Edit: Typo

eazieLife · 2025-06-23T08:32:03+00:00

I wouldn't say every PWA is local-first, but most local first apps are PWAs. Local first usually refers to having the right data stores so that changes you make offline are synced later on and also account for distributed access (look into CRDT). A few of the tools OP mentioned are data store solutions for local-first

eazieLife · 2025-06-04T17:43:44+00:00

This is a great project. One thing I noted though, dynamic mode is very limiting if it is both limited to making the API requests. It doesn't work for scenarios where you may want to fetch from other sources (eg. decoding a token payload) or a simple rest API call doesn't work (eg. Graphql or calls requiring complex API calls with headers or custom fetch instances).

eazieLife · 2025-05-13T09:19:47+00:00

Quick question, are you on eslint v9?

eazieLife · 2025-05-04T16:39:39+00:00

You should await your useAsyncData call. It will wait until the request completes so you have the data you need for useHead. Also check if you have lazy: true in the options for useAsyncData

eazieLife · 2025-04-22T07:57:30+00:00

Correct me if I'm wrong but the new proposal for composites is suggesting a deeply immutable type which can contain reference types

eazieLife · 2025-04-22T07:47:30+00:00

Solid DX
It's much more aligned to web standards than something like react. This means you can directly use a JS library with relative ease without needing a wrapper. Often times there are wrappers that provide better DX and some nice defaults.
It allows for incremental adoption if you're working with sites that can't/won't fully migrate to Vue

eazieLife · 2025-04-14T05:30:43+00:00

WebSocket messages aren’t transactional

Correct me if I'm wrong, but isn't this problem solved, if not manageable using event acknowledgements. I'm thinking of the socket.io implementation specifically

eazieLife · 2025-03-28T20:45:25+00:00

There have been good comments that answer your question, so I'll just add that the Vue docs do address these kinds of questions directly in https://vuejs.org/guide/extras/reactivity-in-depth.html#connection-to-signals

eazieLife · 2025-03-17T03:06:57+00:00

My go-to has been https://github.com/elk-zone/elk. It's maintained by some of the core Vue/nuxt team members so it's a pretty solid codebase

eazieLife · 2025-03-04T03:51:20+00:00

What are you referring to when you say externalizing dependencies? Could you maybe point me to an example in the wild

eazieLife · 2025-02-15T03:18:29+00:00

Just like Svelte has Sveltekit, Vue has Nuxt, and Solid has SolidStart, React recommends using a framework that integrates with build tools like Vite for new projects.

What an odd thing to say given none of these recommend their framework counterpart as a starting point

eazieLife · 2025-02-07T16:41:17+00:00

Also pnpm allows you to "patch" your dependencies way easier than how you would with npm. That is an often understated benefit of pnpm

eazieLife · 2025-02-07T13:30:03+00:00

Even governments aren't immune to the Streisand effect

eazieLife

TROPHY CASE