Steven ⬢
@styfle.dev
🐏 Software Shepherd @vercel.com
💚 Contributor to @nextjs.org @react.dev @nodejs.org @tc39.es
🤵 Husband & Father
✝️ Jesus lover
https://styfle.dev
💚 Contributor to @nextjs.org @react.dev @nodejs.org @tc39.es
🤵 Husband & Father
✝️ Jesus lover
https://styfle.dev
Yeah and also there are some cases where users can’t set CLI flags to even try out the feature, so unflagging allows those users to try the feature too.
November 13, 2025 at 12:34 AM
Yeah and also there are some cases where users can’t set CLI flags to even try out the feature, so unflagging allows those users to try the feature too.
Has anyone tried to change the node:glob implementation to tinyglobby?
November 12, 2025 at 12:55 AM
Has anyone tried to change the node:glob implementation to tinyglobby?
I can’t believe I have to say this - no it’s not a “culture thing”.
You are creating a narrative based on interactions with 2 people.
You are creating a narrative based on interactions with 2 people.
November 3, 2025 at 8:19 PM
I can’t believe I have to say this - no it’s not a “culture thing”.
You are creating a narrative based on interactions with 2 people.
You are creating a narrative based on interactions with 2 people.
There is a huge bug in this codemod that will cause your program to crash.
URL constructor doesn’t work with relative urls.
github.com/nodejs/userl...
URL constructor doesn’t work with relative urls.
github.com/nodejs/userl...
node-url-to-whatwg-url codemod causes app to crash · Issue #249 · nodejs/userland-migrations
My previous comment was not addressed so I'm opening a new issue to track this bug #92 (comment) You can see the input gets transformed into the expected output. However the expected output crashes...
github.com
November 1, 2025 at 6:06 PM
There is a huge bug in this codemod that will cause your program to crash.
URL constructor doesn’t work with relative urls.
github.com/nodejs/userl...
URL constructor doesn’t work with relative urls.
github.com/nodejs/userl...
And it just landed in Node.js too
November 1, 2025 at 6:03 PM
And it just landed in Node.js too
The team would love for you to upgrade as well.
If you’re able, could you file an issue with the steps to reproduce the issue?
If you’re able, could you file an issue with the steps to reproduce the issue?
October 11, 2025 at 8:40 PM
The team would love for you to upgrade as well.
If you’re able, could you file an issue with the steps to reproduce the issue?
If you’re able, could you file an issue with the steps to reproduce the issue?
What issues are you seeing with 15?
October 10, 2025 at 11:04 PM
What issues are you seeing with 15?
Yes. The only change was running the codemod from the blog post:
npx @next/codemod@canary upgrade beta
npx @next/codemod@canary upgrade beta
October 10, 2025 at 7:19 PM
Yes. The only change was running the codemod from the blog post:
npx @next/codemod@canary upgrade beta
npx @next/codemod@canary upgrade beta
If progressive rendering can replace the blur up placeholder, then it will be quite popular on the web.
October 7, 2025 at 8:29 PM
If progressive rendering can replace the blur up placeholder, then it will be quite popular on the web.
That’s the plan once we drop node@20 support, probably next year
October 5, 2025 at 12:41 AM
That’s the plan once we drop node@20 support, probably next year
HTML element: img: sizes: `auto` value | Can I use... Support tables for HTML5, CSS3, etc
caniuse.com
September 26, 2025 at 11:57 PM