Skip to main content

Next.js Basic

 Next.js is a flexible React framework that gives you building blocks to create fast web applications.

In React, event names are camelCased 

npm install react react-dom next  //to get the base code in current folder

Server Components allow developers to better leverage server infrastructure. For example, you can move data fetching to the server, closer to your database.

all components inside the App Router are Server Components by default.

To improve the performance of your application, we recommend moving Client Components to the leaves of your component tree where possible.

For example, you may have a Layout that has static elements (e.g. logo, links, etc) and an interactive search bar that uses state.

Instead of making the whole layout a Client Component, move the interactive logic to a Client Component (e.g. <SearchBar />) and keep your layout as a Server Component. 

Good to know: In Next.js, during the initial page load, both the rendered result of Server Components from the above step and Client Components are pre-rendered on the server as HTML to produce a faster initial page load.

You cannot import a Server Component into a Client Component:

npm run dev // to execute the Next js and launch on the browser

Routing Concept: 

You cannot import a Server Component into a Client Component:

Pages:

 pages/index.js // home page

 pages/blog.js // localhost/blog

 pages/[blogid].js // blog/1

 pages/product/index.js /product

pages/product/[productId]/index.js =>  /product/3

 pages/product/[productId]/review/[reviewId].js =>  /product/3/review/4

For nested routes make folder [product]/[reviewid].js like this, 

Catch ALL routes :

any url which has docs in the url will catch

 pages/docs/[...params].js  // docs/feature/2/content/1

 pages/docs/[[...params]].js  // docs/

Link Component Navigation:

import {Link} from 'next/link'

<Link><a href="/blog">Blog</a></Link>

How to concatenate string with value:

<Link><a href={`/product/${productid}`}>Blog</a></Link>

router.push(/product) // to redirect to another page

 

Pre Rendering : 


 

 

 

 

 

 

Static generation Issues :

 

Comments

Popular posts from this blog

How to span column of custom table in Drupal

If you want to span the column of custom drupal table like below image, Follow the below code to make the header of the table , <?php $header = array('S.N','District', array('data' => '<div class ="house">Household </div><br><span>Rural</span> <p>Urban</p>','colspan' => 2), array('data' => '<div class ="house">Members</div> <br><span>Rural</span> <p>Urban</p>','colspan' => 2), 'Duplicate/Failed Registration', array('data' => '<div class ="house">Pending De duplication </div><br><span>Rural</span> <p>Urban</p>','colspan' => 2), 'Non Un-organised Workers', 'SSID Generated', 'No. of Card Personlised', ); $rows[] = arra...

Drupal 8 : Link actions,Link menus,Link Tasks,Routings

Drupal 8 : Link actions,Link menus,Link Tasks,Routings Link actions Local actions have also been moved out of the hook_menu() system in Drupal 8 .Use actions to define local operations such as adding new items to an administrative list (menus, contact categories, etc). Local actions are defined in a YAML format, named after the module they are defined by. Such as menu_ui.links.action.yml for this example from menu_ui module: menu_ui.link_add:   route_name: menu_ui.link_add   title: 'Add link'   appears_on:     - menu_ui.menu_edit Here, menu_ui.link_add: It is the Unique name of the link action Most likely start with module name, route_name : Name of the route it means when click the link it redirect to this route, appears_on :  An array of route names for this action to be display on. Now how to know the Route name of any internal/external admin pages like below, By through the drupal console we achieve it, drupal debug:router...

Cache In Drupal

Drupal 8 core caching modules: The Internal Page Cache module: this caches pages for anonymous users in the database. Pages requested by anonymous users are stored the first time they are requested and then are reused for future visitors. The Internal Dynamic Page Cache module: This is a key feature that Drupal 7 did not have. Unlike the Internal Page module, the Dynamic Page module aims to speed up the site for both anonymous and logged-in users. How Cache Works in Drupal: There are two modules available in the drupal core 1 - Internal page cache: The Internal Page Cache module caches pages for anonymous users in the database. Pages requested by anonymous users are stored the first time they are requested and then are reused. Configuring the internal page cache :   From the performance page we can set the maximum time how long browsers and proxies may cache pages based on the Cache-Control header. 2 - Internal dynamic page cache: Drupal 8 provides the Dynamic Page Cache m...