Explore tweets tagged as #reactnode
@JobbermanGhana
@Jobbermanghana
20 days
#HiringAlert . Full stack ReactNode developer: Front-end mobile app developer: Backend developer: Direct sales representatives: Social content specialist:
Tweet media one
2
1
3
@iamdillion
dillion - deeecode
1 year
ReactElement vs ReactNode TypeScript
2
4
27
@mattpocockuk
Matt Pocock
2 years
ReactNode vs Element. Let's clear up the confusion. React.ReactNode: Anything a React component can render. JSX, string, null, undefined, number. JSX.Element: Just represents JSX.
Tweet media one
13
85
867
@OyindaJr
Oyin 👩‍💻
1 year
"From optional to dynamic, I'm mastering Advanced Props in TypeScript React!. Optional Props: Flexibility unlocked.String Literals: Precision perfected.Children Props: Nesting made easy.React.ReactNode: Dynamic children demystified.
Tweet media one
Tweet media two
Tweet media three
Tweet media four
1
4
11
@saporito_eth
Saporito
1 year
Been digging into the react repo recently and came across the ReactNode type. I wonder what the story behind the last type is 🤔
Tweet media one
1
0
3
@alfonsusac
Alfon*
7 months
Ever wondered what types of things react can render?. It actually all defined within the `ReactNode` types. As you can see it consists of primitive types, ReactElement and other stuff. The ReactElement type actually contains both native JSX elements (like divs, sections, h1s)
Tweet media one
0
4
23
@JobbermanGhana
@Jobbermanghana
10 days
Hiring now!.Housekeeping attendant: Full-stack ReactNode developer: Vehicle appearance & maintenance officer: Store manager: Executive assistant: #WeAreHiring
Tweet media one
0
0
0
@kasvmi02
フロントエンドエンジニアのゆで卵
1 year
childrenの型って、どれ使えばいいんだろう、、. 1. FCにジェネリクスでPropsWithChildrenを指定して引数の型定義. 2. 引数に直接PropsWithChildren型定義. 3. エイリアスでReactNode型定義
Tweet media one
Tweet media two
Tweet media three
1
0
6
@d151005
nino
1 year
Tips: ReactNodeからテキストを抽出する. MDXの中身を抜いて fuse.js に検索ソースとして渡す際に使用したのでメモ。. via: react-node-to-string.
Tweet media one
0
1
14
@dev_vortex_
DevVortex
2 years
🚀 Day 20: React & TypeScript Simplified!. ReactNode - the superhero of types! In a functional component, we declare a prop like "children: ReactNode." This prop can hold any React element, string, number, or boolean, making your component versatile. 🦸‍♂️💥 . #React.#75HARD
Tweet media one
2
0
4
@honey321998
honey32
1 year
よく考えたら、「props に ReactNode を渡す」だけで Server / Client 間で DI?制御の逆転?みたいなことが出来てしまうの、美しすぎるな…. 十徳ナイフというより箸やこれは.
2
10
139
@Hayao0819
山田ハヤオ🧊
2 years
これがNode.これがElement.これがNodeList.これがHTMLCollection. 全部同じじゃないですか!!.違いますよー.これだから素人はダメだ!もっとよく見ろ!. これがJSX.Element.これがReactElement.これがReactNode.これがReact.FC. (泡を吹いて倒れる).
1
65
293
@sebastienlorber
Seb ⚛️ ThisWeekInReact.com
2 years
TypeScript 5.1 is now in RC 🙌. Improved JSX types for React coming soon 👌.- Support RSC async/await.- Support returning any valid ReactNode (string, array. ).
Tweet media one
0
12
86
@muhimasri
Muhi Masri
1 year
💡 Using ReactNode as a prop type in a #React component is a great way to allow flexibility in what can be passed as a prop. For example, a Card component could take a simple string title or a more advanced h1 element:
Tweet media one
2
1
8
@danielmerja
Daniel Merja (gotogether.ai)
3 months
LLMs and our last engineer all use React.FC instead of just = function. like this:.const SystemNotificationsProvider = function ({.children,.}: {.children: ReactNode.}). not this.const SystemNotificationsProvider: React.FC<{.children: ReactNode.}> = function ({ children }) {
Tweet media one
0
0
0
@honey321998
honey32
2 years
記事を投稿しました! 【React】Context を使う前に #2 コンポジション (ReactNode 型の Props) を使え [設計] on #Qiita
1
7
61
@JiLiZART
Nikolay Kost 🎸 JS Devundefined
1 year
Представляете, используете вы тип React.FC повсеместно. А в React версии 18 берут и убирают оттуда children: ReactNode. А мне и представлять не надо!.
6
0
12
@jaxnode
Jax node.js UG
23 days
Why React.ReactNode Saves Your Props (and JSX.Element Saves Your Returns) by Amit Kumar in @inPlainEngHQ
0
0
0
@dimyasvariant
セイ
1 year
ReactNodeとReactElementの違いってなんだ?.
0
0
6