javascripter

Sorry for the late reply. I'm aware that in some non-Node environments `fs` and `path` are not available, (in next.js and React Native), causing the error you mentioned. I specifically...

`Link`, `Breadcrumbs`, `Tabs`, `Tooltip`, etc have legitimate use cases without event handlers I think. With 'client-only', we cannot do this directly. Considering `Link` is just an accessible `` component replacement,...

> Defining styles directly on an element only looks readable in the most simple of cases. It's true that named styles can be more readable for larger components. However, we...

This also allows react-strict-dom components to be used as React Server Components in Next.js without babel plugin (babel is buggy in Next.js App Dir so this is quite useful).

@necolas https://github.com/javascripter/rsd-next-rsc Here's the repro. I think this PR removes `contexts` export in `dom/index.js` too, not just for native, specifically this line: https://github.com/facebook/react-strict-dom/blob/780779a65314e2b65b4ffed0c0284afaff6e8585/packages/react-strict-dom/src/dom/index.js This `contexts` export prevents Next.js from loading...

@shuding cc @KevinDoughty @boombb12138 I submitted a [PR](https://github.com/shuding/next-view-transitions/pull/11) that fixes this issue & maintain browser navigation transitions. Can you take a look and see if my approach looks good? My...

I'm struggling with this as well. I have multiple Google accounts signed in simultaneously. One account is a Google Workspace account where Bard is not available, and another is a...

At the moment, I'd recommend using a setup similar to StyleX's official example for most production websites, which uses babel-loader + Webpack & PostCSS. I've tested this setup on a...

https://github.com/javascripter/next-scroll-restoration I ended up not using custom scrolling elements for our website so I'm not using it yet in production but here's my attempt at it when I was trying...