-
## π μ΄μ λ΄μ©
μ€νμΌλμ»΄ν¬λνΈ λΌμ΄λΈλ¬λ¦¬λ₯Ό νμ©νμ¬ λ°μνμ μν΄ ν
λ§ μ μ©μ νλ €ν©λλ€.
λν κ°λ₯νλ€λ©΄ κΈλ‘λ² μ€νμΌκΉμ§ μ μ©μμΌλ³΄κ² μ΅λλ€.
μμ§ μμμ΄λ μμ ν μ ν΄μ§μ§ μμ κ²λ€μ΄ μμ΄μ κ·Έ λΆλΆμ μ μ λΉΌκ³ μ§κΈ μ ν΄μ§ κ²λ§ λ£κ² μ΅λλ€.
### ꡬν λ΄μ©
- [ ] μ€νμΌλμ»΄ν¬λνΈ ν
λ§ μ μ©
### π₯οΈκ΄λ ¨ νλ©΄ (μ νμ¬νβ¦
-
- remove daisy ui
- add kiwi@orbit package with custom colors
- create one page with prepared styled components without any logic in them
- It should include
- [ ] answer button
- [ ] all types oβ¦
-
https://github.com/yuna-c/pokemonDex/blob/b165db66df2bda41fcd4fda77266dc5a94deea7a/src/components/dashboard/Dashboard.jsx#L5
곡ν΅μΌλ‘ μ¬μ©λλ μ»΄ν¬λνΈμ κ²½μ° `styles` λλ ν λ¦¬κ° μλ λ³λμ λλ ν 리(Ex. /components/common, /cβ¦
-
Upgrade styled components (breaking changes)
-
I might have missed it in the docs, but could this crate (perhaps /nightly) solve the "encapsulated components" problem that a lot of CSS in Rust crates are challenged with? Currently it's quite the hβ¦
-
I'm considering switching from prettier do dprint on a frontend react project, but one thing is stopping me: pettier formats code in tagged templates for [styled-components](https://styled-components.β¦
-
### Current Behavior
Generating a component using @nx/react:component and style set to "tailwind", generates a styled-components template. This causes TS errors in the newly generated component.
β¦
-
This might be already addressed, but couldn't find the solution. I am styling simple heading component. I am following two different approach:
**Approach 1:**
```
export const StyledHeading β¦
-
## Background
I recently used [styled components](https://styled-components.com/) for the first time, and [it was really nice](https://github.com/datamade/tpc-ihs-noah-map/pull/25/files#diff-233999β¦
-
More of a request but is there any chance we can get an ideal example for using Styled Components with Vite? I tried my hand at it but would love to see something here to go off of.