Загрузка видео...

Не удалось загрузить видео

На главную

ThiingsGrid (the infinite grid component used in thiings[.]co) is now open source! I made a little playground to explore the component. It's a single React+TS file with 0 other dependencies, so easy to drop into your project. Check it out an lmk what you think! Repo 👇

28,075 просмотров • 1 год назад •via X (Twitter)

Комментарии: 11

Фото профиля Charlie Clark
Charlie Clark1 год назад

I'll try to add more examples in the coming days (including a simple animated one like on thiings)

Фото профиля Rainmaker
Rainmaker2 лет назад

Here I share an XGBoost model that delivers a 25% CAGR with minimal drawdown on Visa stock. In this free Substack post I share code and commentary for a powerful Machine Learning strategy that delivers powerful returns.

Фото профиля Mockuuups Studio
Mockuuups Studio1 год назад

Love this! We actually used ThiingsGrid to demo our entire mockup library—over 4,800 scenes! The performance is 🔥 and the integration was seamless.

Фото профиля Leon
Leon1 год назад

🌐 thiings-world

Фото профиля Charlie Clark
Charlie Clark1 год назад

woah trippy!! 💫

Фото профиля Mateo (Melian) 🇦🇷
Mateo (Melian) 🇦🇷1 год назад

Love this, thanks

Фото профиля Luke Berry
Luke Berry1 год назад

this is super, thanks!

Фото профиля Carmen (she/her) 👩🏽‍💻⚡️🦸🏾‍♀️🏳️‍🌈
Carmen (she/her) 👩🏽‍💻⚡️🦸🏾‍♀️🏳️‍🌈1 год назад

Awesome!

Фото профиля Luke Berry
Luke Berry1 год назад

i wonder why it's rendering like this to me? didn't spot any "text-white" classes in the elements

Фото профиля Charlie Clark
Charlie Clark1 год назад

Weird! Just pushed a tweak, any luck now?

Фото профиля Deepak Mehta
Deepak Mehta1 год назад

Well done , will be useful for alot of us.

Похожие видео

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

Delba

43,989 просмотров • 2 лет назад