const exec = require( 'child_process' ) .exec
var yourExecCmd = 'ls -ltr'
// Function to exec shell cmd with callback
function execWithCallback( ) {
this .execCommand = function ( cmd, callback) {
exec( cmd, ( error, stdout, stderr) =& gt; {
if ( error) {
console.error ( `exec error: ${ error} `)
return
}
console.log ( 'stdout:' , stdout)
console.log ( 'stderr:' , stderr)
callback( stdout)
} )
}
}
var execWithCallback = new execWithCallback( )
execWithCallback.execCommand ( yourExecCmd, function ( result) {
console.log ( 'result' )
console.log ( result)
} )
Posted
on September 5, 2024, 2:25 pm,
by admin,
under
nexjs .
Regular import
When using a regular component import, Next.js bundles the component’s code together with the rest of the components for a given route. This usually means you end up with a big chunk containing all the components code for each route.
next/dynamic with ssr: trueWhen using next/dynamic with ssr: true, Next.js splits the component’s code into a separate chunk (code splitting) and loads that chunk separately (lazy loading).
This means that for the scenario that you described:
import dynamic from 'next/dynamic'
const DynamicButton = dynamic( ( ) => import ( './dynamicButton' ) , { ssr: true } )
...
return showButton && < DynamicButton />
The DynamicButton component only gets loaded when showButton is truthy. This has the benefit of reducing the amount of JavaScript that’s loaded on initial page load.
next/dynamic with ssr: falseWhen using next/dynamic with ssr: false, all the above benefits of the dynamic import also apply. However, the component’s code will not get preloaded on the server and will only run on the client. This is typically useful when the component includes a library or API that only works in the browser.
Posted
on July 3, 2024, 4:01 pm,
by admin,
under
nexjs .
Next.Js version 13.4 ( app/ folder ) fetch(URL, { next: { revalidate: 10 } }) – use this one getStaticProps fetch(URL, { cache: ‘no-store’ }) getServerSideProps fetch(URL, { cache: ‘force-cache’ }) getStaticPaths() generateStaticParams()
Posted
on April 1, 2024, 2:03 pm,
by admin,
under
git .
git commit --amend -m "an updated commit message"
Posted
on March 25, 2024, 12:28 pm,
by admin,
under
git .
xs: Extra small devices (less than 600px)sm: Small devices (600px and up)md: Medium devices (900px and up)lg: Large devices (1200px and up)xl: Extra large devices (1536px and up)< Box
sx= { ( theme) => ( {
textAlign: 'center' ,
[ theme.breakpoints .up ( 'md' ) ] : { textAlign: 'left' } ,
} ) }
>
TEXT
</ Box>
theme.breakpoints.up(‘md’) means @media (min-width: 900px)
So, the above code will set the textAlign to left for screen sizes greater than 900px.
Posted
on March 12, 2024, 6:17 pm,
by admin,
under
javascript .
const hostname = "www.someaddress.com"
console.log ( !! hostname.startsWith ( 'www.' ) ? 'matching' : 'not matching' )
Posted
on March 2, 2024, 1:52 pm,
by admin,
under
react .
'use client'
import { usePathname, useParams, useSearchParams} from "next/navigation" ;
// folder structure: app/team/[teamName]/page.tsx
// url: http://localhost:3002/team/something?query=mine
/* Expected output:
Pathname: /team/something
Params: something
SearchParams: mine
*/
export default function Page( ) {
let queryResult: string | null | undefined = null
// params dataset placeholder
let params: Record< string, string | string[ ] > | null
const pathName = usePathname( )
params = useParams( )
const searchParams = useSearchParams( )
queryResult = searchParams? .get ( 'query' )
return (
<>
< div>< span> Pathname: </ span> { pathName} </ div>
< div>< span> Params: </ span> { params? .teamName } </ div>
< div>< span> SearchParams: </ span> { queryResult} </ div>
</>
)
}
Posted
on February 18, 2024, 11:55 am,
by admin,
under
apache .
PROJECT_FOLDER/package.json – configuration of installed packages and their versions
“next”: “^13.2.4” – check nextjs installed version here
PROJECT_FOLDER/tsconfig.json – Typescript configuration
PROJECT_FOLDER/.eslintrc.json – EsLint configuration
PROJECT_FOLDER/postcss.config.js – PostCSS configuration
PROJECT_FOLDER/next.config.js – NextJS configuration
PROJECT_FOLDER/tailwind.config.ts – Tailwind configuration
Three dots {…props} decompiles array and used to merge an array with individual variables
const linkProps = {
...props,
...(customname === true ? { passHref: true } : {})
}