ok sure i get the point but what kind of graph is this
November 23, 2025 at 1:34 PM
ok sure i get the point but what kind of graph is this
apparently clicking links from console.error doesn't work anymore in chrome... on some sites. but it works on others
what the hell. is there a crbug for this?
what the hell. is there a crbug for this?
November 22, 2025 at 10:24 AM
apparently clicking links from console.error doesn't work anymore in chrome... on some sites. but it works on others
what the hell. is there a crbug for this?
what the hell. is there a crbug for this?
@ives.sh looks like something's up with sandpack resolution (?), the sandboxes on the site broke again but they work on codesandbox. one of the versions is resolving to a stale one
example: react.dev/reference/re...
example: react.dev/reference/re...
November 19, 2025 at 1:53 PM
@ives.sh looks like something's up with sandpack resolution (?), the sandboxes on the site broke again but they work on codesandbox. one of the versions is resolving to a stale one
example: react.dev/reference/re...
example: react.dev/reference/re...
okay server stuff now automatically showing up in Performance tab (via RSC debug channel) is actually pretty goated
November 16, 2025 at 1:20 PM
okay server stuff now automatically showing up in Performance tab (via RSC debug channel) is actually pretty goated
hmm pretty sure there's a mistake in lesson 3 worksheet example. the example shows [American] in the question but the answer below is consistent with [I] being in the brackets
![Please use wa in all these sentences. If there is a word in [square
brackets], that word should be the wa-marked topic of the
sentence. This time, please give the answer in four forms: the
three we did before plus the literal English meaning, using “as
for”.
NOTE: wa can only mark something we already know about. So
in cases where “a” or “the” is needed in English, we never
render ○○は“as for a ”. It will always be “as for ○○ the ”. ○○
Example:
Q: I am an [American]
A: わたしはアメリカ人だ (or: watashi wa Amerikajin da)
=わたしは∅がアメリカ人だ (or: =watashi wa -ga ∅
Amerikajin da)
=わたしはわたしがアメリカ人だ (or: =watashi wa
watashi ga Amerikajin da)
As for me, I am an American](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:fpruhuo22xkm5o7ttr2ktxdo/bafkreied2pjmfs3xipfov7nam7xs5ctfnr3ct6ldqv65nbdatatgx2rhfu@jpeg)
November 7, 2025 at 4:18 PM
hmm pretty sure there's a mistake in lesson 3 worksheet example. the example shows [American] in the question but the answer below is consistent with [I] being in the brackets
no, google search is not a dog
November 5, 2025 at 12:17 PM
no, google search is not a dog
it’s not a separate top-level type but you do see it in the tree.
that’s why Prettier reformats them as ("use foo"); if you put them in the wrong place
that’s why Prettier reformats them as ("use foo"); if you put them in the wrong place
November 4, 2025 at 3:31 AM
it’s not a separate top-level type but you do see it in the tree.
that’s why Prettier reformats them as ("use foo"); if you put them in the wrong place
that’s why Prettier reformats them as ("use foo"); if you put them in the wrong place
aargh someone kill me. literally THE WHOLE POINT of directives is that they’re not just strings!
they’re syntactically attached to the scope (function or module) in a way that’s reflected in AST.
and both RSC and Next.js ones act at module boundary which is kinda gross for decorators or API calls
they’re syntactically attached to the scope (function or module) in a way that’s reflected in AST.
and both RSC and Next.js ones act at module boundary which is kinda gross for decorators or API calls
October 29, 2025 at 10:21 PM
aargh someone kill me. literally THE WHOLE POINT of directives is that they’re not just strings!
they’re syntactically attached to the scope (function or module) in a way that’s reflected in AST.
and both RSC and Next.js ones act at module boundary which is kinda gross for decorators or API calls
they’re syntactically attached to the scope (function or module) in a way that’s reflected in AST.
and both RSC and Next.js ones act at module boundary which is kinda gross for decorators or API calls
figured it out. the fix:
this ... was not obvious. would be nice if there a way to "rebuild without cache" or some env variable to turn it off
this ... was not obvious. would be nice if there a way to "rebuild without cache" or some env variable to turn it off
October 28, 2025 at 12:06 PM
figured it out. the fix:
this ... was not obvious. would be nice if there a way to "rebuild without cache" or some env variable to turn it off
this ... was not obvious. would be nice if there a way to "rebuild without cache" or some env variable to turn it off
mathematicians call this “if and only if”
October 26, 2025 at 6:04 PM
mathematicians call this “if and only if”
oof spent an ungodly amount of time trying to get Next.js working with @slices.network OAuth via Claude so to whoever who might run into this later — you need to explicitly redirect with 302, or Next will do it with 307 which (???) breaks OAuth
October 25, 2025 at 5:01 PM
oof spent an ungodly amount of time trying to get Next.js working with @slices.network OAuth via Claude so to whoever who might run into this later — you need to explicitly redirect with 302, or Next will do it with 307 which (???) breaks OAuth
took claude exactly 30 seconds to port the homepage to get data from @slices.network instead of my mock
this is a record from my repo showing!
this is a record from my repo showing!
October 25, 2025 at 3:38 PM
took claude exactly 30 seconds to port the homepage to get data from @slices.network instead of my mock
this is a record from my repo showing!
this is a record from my repo showing!
@tangled.org is sending PRs broken? this is a very confusing and unhelpful error. "failed" why?
October 25, 2025 at 3:11 PM
@tangled.org is sending PRs broken? this is a very confusing and unhelpful error. "failed" why?
sneak peek of a little atproto app i’ve been working on. it’s called sidetrail
it is for sharing “trails”. a trail is a sequence of stops where you do, learn, or think. a trail feels personal — it is whatever “worked for you”
(this is a mockup with fake data)
it is for sharing “trails”. a trail is a sequence of stops where you do, learn, or think. a trail feels personal — it is whatever “worked for you”
(this is a mockup with fake data)
October 25, 2025 at 5:58 AM
sneak peek of a little atproto app i’ve been working on. it’s called sidetrail
it is for sharing “trails”. a trail is a sequence of stops where you do, learn, or think. a trail feels personal — it is whatever “worked for you”
(this is a mockup with fake data)
it is for sharing “trails”. a trail is a sequence of stops where you do, learn, or think. a trail feels personal — it is whatever “worked for you”
(this is a mockup with fake data)
trying to deploy a Next.js app on Railway and the build is failing with obscure error. anyone seen this before?
`npm run build` works fine locally with the same Node version
`npm run build` works fine locally with the same Node version
![Error occurred prerendering page "/drafts". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: c is not a function
at g (.next/server/chunks/ssr/[root-of-the-server]__5413aacc._.js:1:785)
at h (.next/server/chunks/ssr/[root-of-the-server]__5413aacc._.js:1:811)
at Proxy.<anonymous> (.next/server/chunks/ssr/[root-of-the-server]__5413aacc._.js:1:1190)
at m (.next/server/chunks/ssr/[root-of-the-server]__5413aacc._.js:1:6674)
at e (.next/server/chunks/ssr/[root-of-the-server]__5413aacc._.js:1:3277)
at e (.next/server/chunks/ssr/[root-of-the-server]__5413aacc._.js:1:11654) {
digest: '4261865489'
}
Export encountered an error on /(home)/drafts/page: /drafts, exiting the build.
⨯ Next.js build worker exited with code: 1 and signal: null](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:fpruhuo22xkm5o7ttr2ktxdo/bafkreig5czaotyeoiamt522a4qjjat656eaygybytjxeivqvcthys65ox4@jpeg)
October 25, 2025 at 5:27 AM
trying to deploy a Next.js app on Railway and the build is failing with obscure error. anyone seen this before?
`npm run build` works fine locally with the same Node version
`npm run build` works fine locally with the same Node version
i guess that makes us square
October 24, 2025 at 5:26 AM
i guess that makes us square
my favorite AT diagram is this from pfrazee.leaflet.pub/3lyucxaykg22w
i unironically think it nails the topic. other stuff is implementation details and isn’t set in stone
i unironically think it nails the topic. other stuff is implementation details and isn’t set in stone
October 24, 2025 at 12:34 AM
my favorite AT diagram is this from pfrazee.leaflet.pub/3lyucxaykg22w
i unironically think it nails the topic. other stuff is implementation details and isn’t set in stone
i unironically think it nails the topic. other stuff is implementation details and isn’t set in stone
hmm interesting, i did try to use it, but the autosuggestion list doesn't do what i want. i would've expected this to have app.bsy.feed.post, and to *not* have a bunch of other stuff
i guess i could dig for where this happens in the code but i haven't gotten to that stage yet
i guess i could dig for where this happens in the code but i haven't gotten to that stage yet
October 18, 2025 at 12:43 AM
hmm interesting, i did try to use it, but the autosuggestion list doesn't do what i want. i would've expected this to have app.bsy.feed.post, and to *not* have a bunch of other stuff
i guess i could dig for where this happens in the code but i haven't gotten to that stage yet
i guess i could dig for where this happens in the code but i haven't gotten to that stage yet
