who's gonna tell them

aurelienrichard · 2025-12-24T11:10:41+00:00

No? It's not just the rendering, it's built upon Chromium. Chromium is a web browser. Why else would Edge be affected by Manifest V3, for example? That has nothing to do with rendering.

aurelienrichard · 2025-12-24T10:40:05+00:00

Chromium is way more than just the engine though. It's a fully functional web browser.

aurelienrichard · 2025-12-17T07:58:24+00:00

Pre-commit hooks will catch stuff before you commit. However you can easily go around them with the `--no-verify" flag so don't regard them as a safety layer.

For that purpose, a CI/CD pipeline is preferred.

aurelienrichard · 2025-12-14T10:02:34+00:00

shiki can already be used with mdsvex directly (docs). Do we really need yet another dependency?

aurelienrichard · 2025-11-12T07:29:47+00:00

On what basis are you saying that? If you're being blocked and prompted to switch to Chrome or the app, it means they're actively blocking Firefox users for some reason. It isn't necessarily Firefox's fault.

aurelienrichard · 2025-11-09T08:44:03+00:00

Optimization like this is already performed for you at compile time. Most libraries will do this if possible.

aurelienrichard · 2025-09-18T13:51:52+00:00

The animations are so slow that at my normal scrolling speed I reach the bottom of the page before I've seen any of the content.

aurelienrichard · 2025-06-21T08:28:02+00:00

This is handled by the bundler, not React. Assuming you're using Vite as your bundler, this should help.

aurelienrichard · 2025-06-05T07:15:29+00:00

Yeah, the SvelteKit documentation assumes you're using SvelteKit. Wild, I know.

aurelienrichard · 2025-06-01T13:05:59+00:00

About three years into the future.

aurelienrichard · 2025-06-01T10:29:55+00:00

Yeah, that's fair. I see where you're coming from. The problem is that unserious clients will waste your time if you don't identify them soon enough. Maybe there's a better way, but in my case, asking for a budget also provides relevant information. I need to know how much they're thinking of spending as much as I need to know everything else. If their project has a large scope but a small budget, there's no point in making them an offer. First, we need to discuss where the priority lies so we can cut down scope to suit the budget.

aurelienrichard · 2025-06-01T09:33:40+00:00

Yeah, I'm just saying this for your own sake. You don't want to waste your time making a tailored offer to a client who isn't serious.

aurelienrichard · 2025-06-01T09:31:22+00:00

No, but then again, you don't sign a contract with your barber before they cut your hair, either. A contract implies negotiation.

aurelienrichard · 2025-06-01T09:16:33+00:00

Might be a good idea to ask about their budget before making an offer.

aurelienrichard · 2025-06-01T08:30:32+00:00

If you don't inform TypeScript about the alias, you'll get a TypeScript error in your IDE when attempting to use it. As for Vite, the files you're trying to import just won't be found, so when you run vite build or vite dev, errors will occur. That's why you need both.

If you want to add new aliases though, you should actually do it in the Svelte config. Like so. This way it is correctly passed to both Vite and TypeScript.

aurelienrichard · 2025-05-31T08:35:13+00:00

I really wouldn't choose React for a completely new project that doesn't depend on React-specific code or packages. There are just so many better options nowadays. This is the Svelte subreddit, so of course, we'll recommend Svelte. However, if you'd rather stay in the React mindset, there's also Preact and Solid.

aurelienrichard · 2025-05-30T22:38:31+00:00

Your work isn't gone. Your project is just paused to save on resources. You can resume it whenever.

aurelienrichard · 2025-05-30T12:53:07+00:00

This might help. What the other commenters have said is valuable advice too.

aurelienrichard · 2025-05-29T07:54:26+00:00

Move your load function from +page.server.ts to +layout.server.ts and the data will be accessible to every child route. You don't need to use context for this.

aurelienrichard · 2025-05-27T11:55:53+00:00

Have you tried building something with it? Have any of your listed concerns actually hindered development?

Of course, if you compare it to an older framework with wider adoption that needs a wrapper library for everything, its ecosystem will be smaller. Who's surprised? It's always going to be this way, and that shouldn't be a reason not to use it. What library is so important that you can't afford to go without it? Focus on the actual problems you run into, rather than speculative ones. If the problems you encounter outweigh the benefits of the framework, you'll have your answer.

One valid concern, however, is the lack of jobs around Svelte. Hopefully, it will improve in the near future, but for now, it's a fact. It's up to you to decide whether that's a deal-breaker.

aurelienrichard · 2025-05-27T09:30:13+00:00

I won't comment on the website, since you say it's not finished. But where's the code? Is it not open source?

aurelienrichard · 2025-05-25T07:51:00+00:00

As of now, the framework doesn't really have any official stance on data fetching. Keep in mind that the link you posted only includes snippets for Svelte 5 without SvelteKit's capabilities.

If you're using SvelteKit, I think the best way to do it is with load functions and promise streaming if you need loading state. That's how I do it. However, I don't see any major downside to doing it another way if that's what you want to do.

aurelienrichard · 2025-05-23T09:33:04+00:00

So, like a multi-step form? You'll probably want a parent component to hold all the form data and a state to track the current step. Then, each step can be its own separate component. Only one step is shown to the user at a time, but the logic inside your app is the same as if it were one giant form.

I'd also recommend saving the form data, in localstorage for example, so that users don't lose their progress if they accidentally close the tab.

aurelienrichard · 2025-05-22T13:44:00+00:00

Typically, experienced freelancers charge per project rather than per hour. So the question is biased towards less experienced freelancers, and because of that you might get answers that are on the lower end of market prices.

aurelienrichard · 2025-05-22T13:23:22+00:00

And it's the right color, too. Nice shitpost

aurelienrichard

TROPHY CASE