{"id":3931,"date":"2019-04-01T08:53:00","date_gmt":"2019-04-01T08:53:00","guid":{"rendered":"http:\/\/the-codest.localhost\/blog\/why-should-you-use-scss-instead-of-styled-components\/"},"modified":"2026-04-24T11:21:07","modified_gmt":"2026-04-24T11:21:07","slug":"hvorfor-bor-du-bruke-scss-i-stedet-for-stylede-komponenter","status":"publish","type":"post","link":"https:\/\/thecodest.co\/nb\/blog\/why-should-you-use-scss-instead-of-styled-components\/","title":{"rendered":"Hvorfor b\u00f8r du bruke SCSS i stedet for Styled Components?"},"content":{"rendered":"<p>Etter \u00e5 ha sammenlignet popul\u00e6re l\u00f8sninger som vanlig CSS, Emotion, <strong>SCSS <\/strong>og<strong> Stylede komponenter<\/strong>valgte jeg til slutt den siste. Alt s\u00e5 ut til \u00e5 v\u00e6re i orden. Det har et veldig popul\u00e6rt bibliotek n\u00e5 for tiden, noe som betyr<br>det er allerede et stort fellesskap, s\u00e5 hvis jeg skulle m\u00f8te noen problemer, vil jeg sannsynligvis finne en l\u00f8sning et sted p\u00e5 Stack Overflow eller GitHub. Bortsett fra det, <strong>Stylede komponenter<\/strong> har noen optimaliseringsfunksjoner som betyr at de bare gjengis n\u00e5r det er behov for dem. De <a href=\"https:\/\/thecodest.co\/nb\/dictionary\/why-do-projects-fail\/\">prosjekt<\/a> var forventet \u00e5 bli bygget ved hjelp av <a href=\"https:\/\/thecodest.co\/nb\/blog\/conditional-component-visibility-in-react\/\">React<\/a> og <a href=\"https:\/\/thecodest.co\/nb\/dictionary\/typescript-developer\/\">Maskinskrevet manuskript<\/a>. Dette biblioteket har god st\u00f8tte for begge teknologiene. H\u00f8res fantastisk ut, ikke sant?<\/p>\n\n\n\n<p>Da begynte jeg \u00e5 kode. Etter en m\u00e5ned, n\u00e5r appen har vokst, ble frontend <a href=\"https:\/\/thecodest.co\/nb\/blog\/best-practices-for-building-a-strong-and-cohesive-team\/\">team<\/a> og jeg fokuserte p\u00e5 \u00e5 levere funksjoner, fant vi ut at den fantastiske <strong>Stylede komponenter <\/strong>Biblioteket hadde sitt eget m\u00e5l, og jeg skal fortelle deg hvorfor.<\/p>\n\n\n\n<p>F\u00f8rst og fremst navnekonvensjonen. For \u00e5 skille mellom <strong>Stylede komponenter<\/strong> fra <a href=\"https:\/\/thecodest.co\/nb\/blog\/react-development-all-you-have-to-know\/\">React-komponenter<\/a>, m\u00e5tte jeg bruke <code>Stylet<\/code> prefiks som reduserte <a href=\"https:\/\/thecodest.co\/nb\/dictionary\/what-is-code-refactoring\/\">kode<\/a> lesbarhet. Og s\u00e5 (noe som kanskje er merkelig), st\u00f8tte for Typescript. <strong>Stylede komponenter<\/strong>er, som du kanskje vet, basert p\u00e5 CSS-in-JS-tiln\u00e6rmingen. Dette betyr at du kan sende en hvilken som helst prop til dem og endre stilen p\u00e5, dvs. inndataene basert p\u00e5 denne prop, og jeg personlig synes denne funksjonen er fantastisk. I Typescript b\u00f8r du ogs\u00e5 implementere typen av denne prop-en, noe som gj\u00f8r koden lengre <strong>Stylet komponent<\/strong>. \"Men det ville jo tatt fem sekunder til, s\u00e5 hva er problemet ditt?\", sier du kanskje. Du har rett, selv om n\u00e5r appen skaleres opp raskt og antall komponenter er<br>\u00f8ker, kan disse 5 sekundene lett multipliseres med hundrevis av ganger. Et annet problem er plasseringen av <strong>Stylede komponenter<\/strong>.<\/p>\n\n\n\n<p>Noen <strong><a href=\"https:\/\/thecodest.co\/nb\/blog\/hire-vue-js-developers\/\">JS<\/a> utviklere<\/strong> plasserer dem i samme fil som komponenten de tilh\u00f8rer, mens andre oppretter separate filer for dem. Begge tiln\u00e6rmingene er gode av mange grunner. Det avhenger mest av komponentens kompleksitet. Ved \u00e5 f\u00f8lge en av disse teknikkene kan man opprettholde sammenhengen, men ved \u00e5 sl\u00e5 dem sammen oppn\u00e5r man det motsatte. Vi gikk bort fra CSS-i-JS-tiln\u00e6rmingen og gikk over til <a href=\"https:\/\/thecodest.co\/blog\/how-we-care-about-quality-of-css-code\/\">SCSS<\/a>. Det var ikke enkelt og raskt, men med litt hjelp fikk vi det til. Vi begynte \u00e5 style html-tagger i BEM-metodikken og la selvf\u00f8lgelig stilene i separate filer, \u00e9n per komponent. Jeg sa at det \u00e5 sende JS props til <strong>Stylede komponenter<\/strong> er en fantastisk funksjon, men i <strong>SCSS<\/strong> det er umulig. Jeg tror ogs\u00e5 vi alle er enige om at syntaksen React \u00f8nsker for \u00e5 kode betingede klasser er forferdelig.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"\/app\/uploads\/2024\/05\/react-classnames.png\" alt=\"kode for react-klassenavn \" title=\"react-klassenavn\"\/><\/figure>\n\n\n\n<p>Det finnes en ganske interessant l\u00f8sning. Hvis du kobler BEM-metodikken med <code>clsx<\/code> bibliotek, f\u00e5r du noe s\u00e5nt som dette (stor takk til min venn Przemek Adamczyk for \u00e5 ha vist meg dette biblioteket)<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"\/app\/uploads\/2024\/05\/will-clsx.png\" alt=\"clsx-kode\" title=\"eksempel p\u00e5 clsx-kode\"\/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Ser mye renere ut, synes du ikke?<\/h2>\n\n\n\n<p>Det beste er at du bare trenger \u00e5 skrive inn tilstandsvariabelen p\u00e5 komponentniv\u00e5 og<br>ikke p\u00e5 stylingniv\u00e5. Det sparer virkelig tid. Dessverre har en slik l\u00f8sning sine ulemper.<br><strong>SCSS<\/strong> er enkelt og brukervennlig, men v\u00e6r forsiktig n\u00e5r du bruker det med Next.js. Dette rammeverket er ikke<br>gj\u00f8r det mulig \u00e5 importere stilfiler direkte inn i komponentfilen (kun CSS-moduler).<\/p>\n\n\n\n<p>Hvis du foretrekker \u00e9n fil per komponent, m\u00e5 du opprette <code>index.scss<\/code> som inneholder alle dine <strong>SCSS<\/strong> filer og<br>importere den inn i <code>_app.tsx<\/code> filen. Det eneste problemet er at du m\u00e5 importere hver <strong>SCSS<\/strong> filen du har opprettet. I React eksisterer imidlertid ikke dette problemet, og du kan importere <strong>SCSS<\/strong> filer hvor du vil. Ikke misforst\u00e5 meg. <strong>Stylede komponenter<\/strong> er virkelig bra. Som jeg sa tidligere, er det \u00e5 overf\u00f8re JS-variabler samt det globale temaet fantastiske funksjoner. N\u00e5r du bygger en stor app der optimalisering er avgj\u00f8rende, vil dette biblioteket sannsynligvis oppfylle dine behov. I v\u00e5rt tilfelle vil imidlertid migrering til <strong>SCSS<\/strong> fikk jackpot.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Oppsummering<\/h2>\n\n\n\n<p>Selv om det finnes gode argumenter for begge deler <strong>SCSS og stiliserte komponenter <\/strong> i <strong><a href=\"https:\/\/thecodest.co\/nb\/blog\/find-your-node-js-expert-for-hire-today\/\">webutvikling<\/a> <\/strong>avhenger den endelige avgj\u00f8relsen av en rekke faktorer. <strong>SCSS <\/strong> tilbyr en mer kjent syntaks for <strong>utviklere med erfaring <\/strong> i tradisjonell CSS og gir en s\u00f8ml\u00f8s integrasjon med eksisterende <strong>kodebaser <\/strong> og <strong>komponentbiblioteker <\/strong>.<\/p>\n\n\n\n<p>P\u00e5 den annen side.., <strong>Stylede komponenter <\/strong> tilby forbedret <strong>utviklererfaring <\/strong> med sin evne til \u00e5 innkapsle stiler i komponenter og forenkle stylingprosessen. Det fremmer ogs\u00e5 kodemodularitet og gjenbrukbarhet, noe som gj\u00f8r det mulig for front-end <a href=\"https:\/\/thecodest.co\/nb\/blog\/team-extension-guide-software-development\/\">Ingeni\u00f8rer<\/a> for effektivt \u00e5 administrere <strong>komponentkatalog <\/strong> og skape et konsekvent brukergrensesnitt p\u00e5 tvers av <strong><a href=\"https:\/\/thecodest.co\/nb\/blog\/find-your-ideal-stack-for-web-development\/\">nett<\/a> app <\/strong>. Tatt i betraktning viktigheten av <strong>bruker <a href=\"https:\/\/thecodest.co\/nb\/blog\/app-data-collection-security-risks-value-and-types-explored\/\">data<\/a> <\/strong> sikkerhet og ytelse, er det avgj\u00f8rende \u00e5 vurdere hvordan begge metodene p\u00e5virker den endelige pakkest\u00f8rrelsen og lastetiden. Til syvende og sist er valget mellom <strong>SCSS og stiliserte komponenter <\/strong> b\u00f8r v\u00e6re basert p\u00e5 prosjektets spesifikke behov, kompetansen til de ansatte <strong><a href=\"https:\/\/thecodest.co\/nb\/blog\/how-to-hire-the-best-outsourced-development-team-for-a-scaleup\/\">utviklingsteam<\/a> <\/strong>og de overordnede m\u00e5lene for <strong> webapplikasjon <\/strong>. Det anbefales at utviklere vurderer alle faktorene, holder seg oppdatert gjennom <strong>blogginnlegg <\/strong> og bransjediskusjoner, og ta en informert beslutning som er i tr\u00e5d med prosjektkravene deres og forbedrer den generelle <strong>front-end <a href=\"https:\/\/thecodest.co\/nb\/blog\/what-to-look-for-in-a-custom-software-development-company\/\">utviklingsprosess<\/a> <\/strong>.<\/p>","protected":false},"excerpt":{"rendered":"<p>De siste par m\u00e5nedene har jeg jobbet med et prosjekt for en av kundene v\u00e5re. Helt i begynnelsen sto jeg overfor et valg av bibliotek for styling.<\/p>","protected":false},"author":2,"featured_media":3932,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[8],"tags":[],"class_list":["post-3931","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-development"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.3 (Yoast SEO v27.3) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Why Should You Use SCSS Instead of Styled Components? - The Codest<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/thecodest.co\/nb\/blogg\/hvorfor-bor-du-bruke-scss-i-stedet-for-stylede-komponenter\/\" \/>\n<meta property=\"og:locale\" content=\"nb_NO\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why Should You Use SCSS Instead of Styled Components?\" \/>\n<meta property=\"og:description\" content=\"For the last couple of months, I\u2019ve been working on a project for one of our clients. When I was at very beginning, I faced a choice of the library for styling.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/thecodest.co\/nb\/blogg\/hvorfor-bor-du-bruke-scss-i-stedet-for-stylede-komponenter\/\" \/>\n<meta property=\"og:site_name\" content=\"The Codest\" \/>\n<meta property=\"article:published_time\" content=\"2019-04-01T08:53:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-24T11:21:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/scss_stc.png\" \/>\n\t<meta property=\"og:image:width\" content=\"960\" \/>\n\t<meta property=\"og:image:height\" content=\"540\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"thecodest\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"thecodest\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutter\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/\"},\"author\":{\"name\":\"thecodest\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/person\\\/7e3fe41dfa4f4e41a7baad4c6e0d4f76\"},\"headline\":\"Why Should You Use SCSS Instead of Styled Components?\",\"datePublished\":\"2019-04-01T08:53:00+00:00\",\"dateModified\":\"2026-04-24T11:21:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/\"},\"wordCount\":820,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/scss_stc.png\",\"articleSection\":[\"Software Development\"],\"inLanguage\":\"nb-NO\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/\",\"url\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/\",\"name\":\"Why Should You Use SCSS Instead of Styled Components? - The Codest\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/scss_stc.png\",\"datePublished\":\"2019-04-01T08:53:00+00:00\",\"dateModified\":\"2026-04-24T11:21:07+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#breadcrumb\"},\"inLanguage\":\"nb-NO\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"nb-NO\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#primaryimage\",\"url\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/scss_stc.png\",\"contentUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/05\\\/scss_stc.png\",\"width\":960,\"height\":540},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/blog\\\/why-should-you-use-scss-instead-of-styled-components\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/thecodest.co\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why Should You Use SCSS Instead of Styled Components?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#website\",\"url\":\"https:\\\/\\\/thecodest.co\\\/\",\"name\":\"The Codest\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/thecodest.co\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"nb-NO\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#organization\",\"name\":\"The Codest\",\"url\":\"https:\\\/\\\/thecodest.co\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"nb-NO\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/03\\\/thecodest-logo.svg\",\"contentUrl\":\"https:\\\/\\\/thecodest.co\\\/app\\\/uploads\\\/2024\\\/03\\\/thecodest-logo.svg\",\"width\":144,\"height\":36,\"caption\":\"The Codest\"},\"image\":{\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/pl.linkedin.com\\\/company\\\/codest\",\"https:\\\/\\\/clutch.co\\\/profile\\\/codest\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/thecodest.co\\\/#\\\/schema\\\/person\\\/7e3fe41dfa4f4e41a7baad4c6e0d4f76\",\"name\":\"thecodest\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"nb-NO\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g\",\"caption\":\"thecodest\"},\"url\":\"https:\\\/\\\/thecodest.co\\\/nb\\\/author\\\/thecodest\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Hvorfor b\u00f8r du bruke SCSS i stedet for stylede komponenter? - The Codest","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/thecodest.co\/nb\/blogg\/hvorfor-bor-du-bruke-scss-i-stedet-for-stylede-komponenter\/","og_locale":"nb_NO","og_type":"article","og_title":"Why Should You Use SCSS Instead of Styled Components?","og_description":"For the last couple of months, I\u2019ve been working on a project for one of our clients. When I was at very beginning, I faced a choice of the library for styling.","og_url":"https:\/\/thecodest.co\/nb\/blogg\/hvorfor-bor-du-bruke-scss-i-stedet-for-stylede-komponenter\/","og_site_name":"The Codest","article_published_time":"2019-04-01T08:53:00+00:00","article_modified_time":"2026-04-24T11:21:07+00:00","og_image":[{"width":960,"height":540,"url":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/scss_stc.png","type":"image\/png"}],"author":"thecodest","twitter_card":"summary_large_image","twitter_misc":{"Written by":"thecodest","Est. reading time":"5 minutter"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#article","isPartOf":{"@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/"},"author":{"name":"thecodest","@id":"https:\/\/thecodest.co\/#\/schema\/person\/7e3fe41dfa4f4e41a7baad4c6e0d4f76"},"headline":"Why Should You Use SCSS Instead of Styled Components?","datePublished":"2019-04-01T08:53:00+00:00","dateModified":"2026-04-24T11:21:07+00:00","mainEntityOfPage":{"@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/"},"wordCount":820,"commentCount":0,"publisher":{"@id":"https:\/\/thecodest.co\/#organization"},"image":{"@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#primaryimage"},"thumbnailUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/scss_stc.png","articleSection":["Software Development"],"inLanguage":"nb-NO","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/","url":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/","name":"Hvorfor b\u00f8r du bruke SCSS i stedet for stylede komponenter? - The Codest","isPartOf":{"@id":"https:\/\/thecodest.co\/#website"},"primaryImageOfPage":{"@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#primaryimage"},"image":{"@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#primaryimage"},"thumbnailUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/scss_stc.png","datePublished":"2019-04-01T08:53:00+00:00","dateModified":"2026-04-24T11:21:07+00:00","breadcrumb":{"@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#breadcrumb"},"inLanguage":"nb-NO","potentialAction":[{"@type":"ReadAction","target":["https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/"]}]},{"@type":"ImageObject","inLanguage":"nb-NO","@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#primaryimage","url":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/scss_stc.png","contentUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/05\/scss_stc.png","width":960,"height":540},{"@type":"BreadcrumbList","@id":"https:\/\/thecodest.co\/blog\/why-should-you-use-scss-instead-of-styled-components\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/thecodest.co\/"},{"@type":"ListItem","position":2,"name":"Why Should You Use SCSS Instead of Styled Components?"}]},{"@type":"WebSite","@id":"https:\/\/thecodest.co\/#website","url":"https:\/\/thecodest.co\/","name":"The Codest","description":"","publisher":{"@id":"https:\/\/thecodest.co\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/thecodest.co\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"nb-NO"},{"@type":"Organization","@id":"https:\/\/thecodest.co\/#organization","name":"The Codest","url":"https:\/\/thecodest.co\/","logo":{"@type":"ImageObject","inLanguage":"nb-NO","@id":"https:\/\/thecodest.co\/#\/schema\/logo\/image\/","url":"https:\/\/thecodest.co\/app\/uploads\/2024\/03\/thecodest-logo.svg","contentUrl":"https:\/\/thecodest.co\/app\/uploads\/2024\/03\/thecodest-logo.svg","width":144,"height":36,"caption":"The Codest"},"image":{"@id":"https:\/\/thecodest.co\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/pl.linkedin.com\/company\/codest","https:\/\/clutch.co\/profile\/codest"]},{"@type":"Person","@id":"https:\/\/thecodest.co\/#\/schema\/person\/7e3fe41dfa4f4e41a7baad4c6e0d4f76","name":"thecodest","image":{"@type":"ImageObject","inLanguage":"nb-NO","@id":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5dbfe6a1e8c86e432e8812759e34e6fe82ebac75119ae3237a6c1311fa19caf4?s=96&d=mm&r=g","caption":"thecodest"},"url":"https:\/\/thecodest.co\/nb\/author\/thecodest\/"}]}},"_links":{"self":[{"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/posts\/3931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/comments?post=3931"}],"version-history":[{"count":9,"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/posts\/3931\/revisions"}],"predecessor-version":[{"id":8166,"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/posts\/3931\/revisions\/8166"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/media\/3932"}],"wp:attachment":[{"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/media?parent=3931"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/categories?post=3931"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thecodest.co\/nb\/wp-json\/wp\/v2\/tags?post=3931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}