Alfredo Lopez

VP, Engineering @Hearst, Drummer, Droid. Trying stuff until it works. Views are mine and always isomorphic. He/him.

[Alfredo Lopez @lfredolo]

@photomatt @wpengine @WordPress *taps the sign*

[Alfredo Lopez @lfredolo]

I'm fully aware that there are probably edge cases for both of these, but it's so great that custom-ish features can be done now. Codex did both of these in a few hours.

Can you imagine if things like this could have been supported near launch? Emotion just works. 🫳🎤

[Alfredo Lopez @lfredolo]

The Bun rewrite and TanStack inspired me to do what I've been waiting for, literally years, in Next/React.

In Next, the lifecycle hooks of _document in App Router. i.e., let me hook up RSC + server rendering before flushing the initial chunk. 🙌

In React, unlock RSC context! 🙏

[Alfredo Lopez @lfredolo]

To support the RSC context, all React needs to do is allow exporting getServerTreePath, and the rest can be done in userland.

React already has `currentlyRenderingTask` internally. Can't fit the whole patch in a screenshot, but you get the gist.

[Alfredo Lopez @lfredolo]

@bstaples Right. My point is ship some adapter/codemod that does this. Make it a no-brainer.

Also gitlab-ci.yml is one file. Modularizing with include is not great.

.gitlab/*.yml is the way to go.

[Alfredo Lopez @lfredolo]

@Steve8708 This is timely! I’m basically building this in-house. Do you support bringing our own agents and hook to other sources like Microsoft Teams?

[Alfredo Lopez @lfredolo]

@ScriptedAlchemy Ah got it, so technically it’s all bc they bundled webpack? If I were to patch Next to remove that and the require hooks, it would work?

I’m already patching Next for other things so I’d be highly interested in that.

[Alfredo Lopez @lfredolo]

@Kpaxs The biggest nuance here, when you fix something, you want to be the "Glue" and not the "Gap Filler".

You can fix/do something while bringing people together (even if it isn't really required), and it makes a world of difference.

[Alfredo Lopez @lfredolo]

@brianchaley Ocean waves. Ocean waves.

[Alfredo Lopez @lfredolo]

@VicVijayakumar This is the equivalent of getting up from the couch after sitting for a while. Everything's good, but give me a sec!

[Alfredo Lopez @lfredolo]

@Una 🙌🏻

[Alfredo Lopez @lfredolo]

@_AhmadAwais @jaredpalmer I ask them to explain their *best* work/invention/etc, then ask if they had to do it all over again, what they would change.

Folks who are both proud of their past work and, at the same time, the most critical about it in hindsight are, IMO, the ones who most display this trait.

[Alfredo Lopez @lfredolo]

@addyosmani @googlechrome What an incredible run, Addy!

The whole dev community (especially web perf!) is immesurably better thanks to your contributions!

Congrats! 🙇🙌

[Alfredo Lopez @lfredolo]

I’d honestly pay a premium for a movie theater experience where people are required to put their phones in a faraday cage bag.

I’m sure the Alamo Drafthouse figured out it’s easier/cheaper to have someone monitor, but one can hope @AMCTheatres 🙏

[Alfredo Lopez @lfredolo]

@_bgwoodruff @timneutkens That’s great to know, even though the docs don’t reflect that sentiment.

Looking forward to get on board when that lands!

[Alfredo Lopez @lfredolo]

Wait, so Turbopack has no Plugin API or plans to do so? For some reason, I thought babel plugins was the dealbreaker from early on, but no compilation hooks at all? Huge bummer.

[Alfredo Lopez @lfredolo]

@timneutkens We've been struggling with how Next now hardcodes ENV and assetPrefix at build time.

Dynamic ENV is much easier, but we had to create a plugin to support a dynamic asset prefix.

Amazingly, you can do this sort of thing in Webpack. https://t.co/vg1bFxgOxu

[Alfredo Lopez @lfredolo]

@timneutkens My bad, this is kind of what I gathered from v0, which reads a bit differently.

Still, you're confirming it's nowhere near the roadmap, which isn't great.

Not every use case should be supported upstream, which is the whole point of providing lifecycle hooks.