Next.js tsarin React ne don fassarar uwar garke, wanda mahaliccinsa ke gabatar dashi azaman daidaita siffofin tsari guda ɗaya na kayan aiki don Amfani da aikace-aikace.
Wannan firam yana ba da tsari na gama gari wanda zai ba ku damar ƙirƙirar aikace-aikacen ƙarshen gaba kuma a bayyane yake sarrafa ma'anar uwar garke. Next.js version 9.3 an sake shi a ranar Litinin tare da sabbin abubuwa da wasu ci gaba, wanda zamu iya samun ikon samar da shafuka tsayayyu a matsayin babban sabon abu.
Menene sabo a Next.js 9.3?
Tare da fitowar Next.js 9.0, tsarin ya gabatar da manufar ingantawa ta atomatik a tsaye. Lokacin da shafi ba shi da bukatun toshewa - dawo da bayanai kamar getInitialProps, zai bayar ta atomatik a cikin HTML da zarar an gina shi.
Akwai wasu lokuta inda zaku so yin shafi a tsaye HTML a tattara lokaci, koda tare da toshe buƙatun cire bayanai. Wannan lamarin haka ne, misali, na shafukan talla ana amfani da shi ta tsarin sarrafa abun ciki (CMS).
Next.js 9.3 yana gabatar da sababbin hanyoyin dawo da bayanai guda biyu: samuStaticProps da samunServerSideProps.
Waɗannan sabbin hanyoyin suna da fa'idodi da yawa akan samfurin getInitialPropstunda akwai bayyanannen bambanci tsakanin abin da zai zama SSG (Static Side Generation) da kuma SSR (Server Side Rendering). APIarin API ne.
Duk sababbin sifofi suna dacewa da baya kuma za'a iya karbarsa a hankali. Babu raguwa kuma getInitialProps yana ci gaba da aiki kullum. An ƙara ma'aunin getStaticPaths don samun jigilar hanyoyi.
- getStaticProps: yana bada damar samun bayanai yayin gini;
- getStaticPaths - Saka bayanai masu dogaro da bayanai;
- getServerSideProps: yana baka damar samun bayanai don kowane buƙata.
Wani canjin da yayi fice daga wannan sabon sigar shine tallafi don yanayin samfoti. Gabatar da getStaticProps a Next.js ya buɗe sababbin hanyoyin, kamar yin amfani da damar Next.js na bayarwa akan buƙata a ƙarƙashin wasu yanayi.
Alal misali, lokacin samfoti daftarin aiki A cikin CMS, zaku so ƙetare fassarar tsaye kuma ba da shafi a kan buƙata tare da abubuwan da aka tsara maimakon abun da aka buga. Kuna son Next.js ya tsallake tsararren gini kawai a cikin wannan takamaiman lamarin. Dangane da ƙungiyar Next.js, yanayin samfoti yana ba ku damar yin wannan.
Yanayin samfoti yana bawa masu amfani damar tsallake shafin da aka samar a zahiri don dawowa kan buƙata (SSR) wani shafi mai ƙira, misali daga CMS. Koyaya, ba'a iyakance shi ga wasu tsarin CMS ba. Yanayin samfoti yana haɗa kai tsaye tare da getStaticProps da getServerSideProps don haka ana iya amfani dashi tare da kowane nau'in maganin dawo da bayanai.
Next.js 9.2 ya ƙara tallafi don ginannen CSS, amma Next.js 9.3 ya ƙara tallafi ga Sass. Ana tallafawa goge-zanen salon duniya da kayayyaki CSS, tare da shigar CSS. Next.js yanzu yana tallafawa ɗakunan CSS tare da fayilolin Sass ta amfani da [name] .module.scss fayil din suna. Ba kamar tallafi da aka samu a baya ba a cikin Next.js 5 + tare da na gaba-sass, sassan duniya na Sass da CSS yanzu suna iya zama tare.
Kayayyaki CSS suna baka damar sarrafa Sass ta gida ta atomatik ƙirƙirar sunayen aji na musamman.
Tare da sigar 9.0 daga Next.js, akwai wani shafi wanda ba a sanya shi ta atomatik a cikin HTML tsaye: shafi 404.
Babban dalili a baya wannan shine cewa shafin kuskuren ciyar da 404 an sarrafa shi fiye da 404. Misali, shi ma ya magance kurakurai. Tunda an sanya shafuka 404 don hanyoyin da babu su, sanya shafi akan buƙata na iya haifar da tsada da haɓaka mai girma sabar. Tsarin 9.3 na Tsarin aiki yana inganta abubuwa kuma yana ba da ingantaccen tsayayyen atomatik don shafuka 404.
Yanzu lokacin da buƙatarku ba ta haɗa da shafin al'ada error.js ba, fayil ɗin Next.js yana samar da shafi 404 kai tsaye ta atomatik kuma yana amfani dashi lokacin da yakamata ayi amfani da 404. Wannan yana faruwa kai tsaye kuma ba a buƙatar canje-canje.
Hakanan zaka iya tsara wannan shafin. Don maye gurbin tsoho shafi na 404, zaka iya ƙirƙirar fayil 404.js.
Idan kana son karin bayani game da shi, zaka iya tuntuba mahada mai zuwa.