Nick Muller

618 posts

Nick Muller

Nick Muller

@nphmuller

Venlo, Nederland Katılım Ocak 2014
1.4K Takip Edilen54 Takipçiler
Nick Muller
Nick Muller@nphmuller·
@housecor I agree. Tried to convince some teams in the past for the reasons you stated. But often we got into all kinds of discussions about details like tooling and project structures. Languages have different standards and it was really hard to convince others to deviate from them.
English
0
0
1
135
Cory House
Cory House@housecor·
@nphmuller One. If I’m likely to change both for most changes, then they belong together so I can make a single PR that groups and tests related changes.
English
1
0
4
713
Cory House
Cory House@housecor·
I’m working with a company that has 40 repos for one app. UI repo Test repo Logic repo DB scripts repo Etc All for the same app! Sure, monorepos have their tradeoffs. But needless decomposition = needless friction. Colocate stuff that changes together.
English
40
7
236
34.6K
Nick Muller
Nick Muller@nphmuller·
@mjovanovictech So many Cartesian explosions when they changed the default from split queries to single queries in EF Core 5. 😅
English
0
0
0
193
Milan Jovanović
Milan Jovanović@mjovanovictech·
Did you try out EF Core Query Splitting? It's an EF Core 5 feature that allows you to tell EF to split a given LINQ query into multiple SQL queries. By default, EF tries to send one query to the database. This can include JOINs when loading related entities. Where's the value?
Milan Jovanović tweet media
English
5
6
59
5.9K
Nick Muller
Nick Muller@nphmuller·
@zeeg Like it a lot, but wish it was easier to open on mobile. On iOS safari i first have to click menu, back, explore. Now the traces view opens with search in focus, but safari annoyingly zooms in. So now I have to zoom out, click menu again and now I can finally click on logs.
English
1
0
2
391
David Cramer
David Cramer@zeeg·
Folks using our logging product, especially folks who are early stage, what do you wish was easier, or that we'd change?
English
16
5
33
7.2K
Nick Muller
Nick Muller@nphmuller·
@orcdev Awesome! The main thing that’s not explicitly mentioned and leaves me wondering: the static shell is still returned by a process (lambda, container, etc) and not by something that can be easily placed behind a cdn (s3 bucket), right @feedthejim @nextjs ?
English
0
0
0
16
OrcDev
OrcDev@orcdev·
Update: We have the docs nextjs.org/docs/app/getti…
OrcDev@orcdev

Next.js 16 is finally stable! ⚔️ The biggest change? Cache Components. BUT… it's still wrapped in mystery 👀 There's no official documentation yet on how to actually use them, so I'm guessing we'll get the full reveal at the upcoming Next.js Conf. Other than that, MCP is a great addition, and we're finally seeing all those Turbopack and React Compiler goodies we tested in beta. Oh, and yes: middleware → proxy

English
2
0
11
709
Nick Muller
Nick Muller@nphmuller·
@bgub_ @nextjs Thank you so much, and really impressive work! These features were all in the top of my nextjs wish list! 😁
English
1
0
1
73
Ben Gubler
Ben Gubler@bgub_·
My intern project just shipped in @nextjs 15.5! I spent the summer on framework improvements: adding Turbopack support for statically typed links and route validation; automatically generating route types; and improving typechecking and linting. Read more: 🧵 1/x
English
17
8
148
14.3K
Nick Muller
Nick Muller@nphmuller·
@timneutkens @JimsonRai @HeyMarkKop Is there something I can use to track this? I searched for an issue on GitHub but I couldn’t find one. Or maybe even a small roadmap of topics that are still planned for turbopack? Currently I’m just watching changes that land in canary.
English
1
0
0
65
Tim
Tim@timneutkens·
@JimsonRai @HeyMarkKop Sourcemaps work, it’s just the specific debugIds feature that Sentry has. We’re still going to work on adding that as a general bundler feature
English
1
0
0
122
Mark Kop
Mark Kop@HeyMarkKop·
I'm basically waiting for react compiler and sentry nextjs turbopack support to upgrade next. Been a while now
English
2
0
2
1.5K
Nick Muller
Nick Muller@nphmuller·
@timneutkens Congrats! Refreshing the page was especially exciting the last couple of days.
English
0
0
1
54
Tim
Tim@timneutkens·
Excited to share "next build --turbopack" is now passing all Next.js test suites! areweturboyet.com
Tim tweet media
English
43
65
1K
82.8K
Nick Muller
Nick Muller@nphmuller·
@kettanaito Man, this is pretty awesome. This example made it perfectly click in my head in what great ways yield might be used. Web native suspense..!
English
1
0
1
167
Artem Zakharchenko
Artem Zakharchenko@kettanaito·
Sometimes I like spending an afternoon designing an API that won't likely lead anywhere. Great mind exercise. Wanna guess what this is?
Artem Zakharchenko tweet media
English
5
0
16
2.6K
Nick Muller
Nick Muller@nphmuller·
@housecor If I see one of your posts I can be sure it’s something interesting or insightful. It’s why I look forward to reading a post if I see your name above it. I don’t see the opposite happening for a post made by AI. Thank you for all the content over the years!
English
1
0
5
429
Cory House
Cory House@housecor·
Confession: The last year has been hard for me. AI has me feeling uneasy about my software development career. Part of me thinks "Why bother if an AI may do it better soon?" But for now, AI can't replace us. So for now, I keep pushing.
English
41
1
228
17.8K
Nick Muller
Nick Muller@nphmuller·
@housecor I often struggle to decide when to use an assertion function, because it’s so easy to make it lie to typescript. I guess a solution could be to write tests for the assertion function as well? But if I write tests I might as well write a zod schema.
English
1
0
2
292
Cory House
Cory House@housecor·
Problem: You have complex logic for narrowing a TypeScript type that you'd like to reuse in a few spots. Solution: Consider an assertion function.
English
8
11
130
10.4K
Nick Muller
Nick Muller@nphmuller·
@rauchg @v0 It looks great, but there was also something nice about seeing it generate the entire file.
English
0
0
0
17
Guillermo Rauch
Guillermo Rauch@rauchg·
Love the new @v0 loading animation. Fun fact, it was conceived with @v0.
English
38
9
712
85.4K
Nick Muller
Nick Muller@nphmuller·
@code Curious if this can finally replace Azure Data Studio’s Postgres plugin for me 😁
English
2
0
5
1.9K
Visual Studio Code
Visual Studio Code@code·
Meet the new Microsoft PostgreSQL extension for @code - packed with powerful tools to supercharge your PostgreSQL workflow, like: 🤖 Agent mode integration 💡 Schema visualization ⚡ Instant Docker PostgreSQL 🔎 IntelliSense-powered queries Learn more: aka.ms/Blog/PostgreSQ…
English
35
369
3.5K
246.2K
Nick Muller
Nick Muller@nphmuller·
@TkDodo I think StaleTime.Static is way easier to understand than the nuances of ensureQueryData.
English
0
0
4
670
Dominik 🔮
Dominik 🔮@TkDodo·
📢 I wrote an RFC about unifying the imperative methods we have on the QueryClient. I think the distinction we have now is quite confusing, especially to newcomers, and we can and should do better. Please let me know what you think in the comments 🙏 github.com/TanStack/query…
English
9
30
351
51.6K
Nick Muller
Nick Muller@nphmuller·
@housecor Would you still prefer vitest for testing react components via browser mode? Bun only supports jsdom at the moment, right?
English
1
0
1
285
Cory House
Cory House@housecor·
Just converted a small test suite from Vitest to bun:test. Bun is about 2x faster. Vitest: 575ms Bun: 273ms And since bun:test syntax is similar to Jest/Vitest and it has TypeScript and JSX support built in, the conversion was easy:
Cory House tweet media
English
20
6
278
24K
Jimmy Lai
Jimmy Lai@feedthejim·
dear self-hosted users of Next.js, what can we do to make your life easier?
English
89
30
542
122.8K
Robin Wieruch
Robin Wieruch@rwieruch·
👀 React 19 Insight How to show a toast notification with callback functions on React's useActionState Hook without relying on React's useEffect. This overhaul has been created following an insightful discussion with Sebastien Lorber yesterday. He suggested an improved solution to my original approach which relies on callbacks 👇
Robin Wieruch tweet media
English
19
90
906
78.3K
Jimmy Lai
Jimmy Lai@feedthejim·
I’ve been wanting to improve error handling in Next.js for a long time, and this release is a huge step forward. A sleek UI, clearer messages, and real fixes, not just weird cryptic errors. And this is just the foundation… Next.js Devtools are on the way!
Next.js@nextjs

Next.js 15.2 • Redesigned Error UI & Improved Stack Traces • Streaming Metadata • Turbopack Performance Improvements • View Transitions (experimental) • Node.js Middleware (experimental) nextjs.org/blog/next-15-2

English
5
5
186
12.1K
Nick Muller
Nick Muller@nphmuller·
@feedthejim @mightyhologram With dynamicIO the pattern basically becomes: async page (with await calls) -> dynamic. Otherwise -> static. Do I understand this correctly?
English
1
0
0
61

Keşfet

@housecor @mjovanovictech @zeeg @orcdev @feedthejim @nextjs @bgub_ @timneutkens