m3h3d1ha2an

According to discussions and trends on X (Twitter) and recent web sources in early 2026, for building small-scale TypeScript sites like landing pages, portfolio pages, company/agency/organization sites (2-3 pages), and especially those with a blog, the community strongly leans toward performance-first, content-oriented meta-frameworks.

The top contenders are Astro (often praised as the winner for this exact use case), Next.js (still the safe, versatile default), and SvelteKit (for joyful DX and tiny bundles). Remix appears less frequently for purely content/marketing sites.

Here's a breakdown focused on your needs (landing/portfolio + blog), including DX (developer experience), UX (end-user experience via speed/responsiveness), and SEO:

1. Astro (Strongest Recommendation for Your Use Case)

Astro dominates 2025–2026 discussions for content-heavy, mostly static sites like portfolios, marketing/landing pages, company sites, and blogs.

• *Why it fits perfectly

m3h3d1ha2an

1. What causes a React component to re-render? ( একটি React কম্পোনেন্ট কেন রি-রেন্ডার হয়? )

Answer: A React component generally re-renders when its state, props, or parent changes, though specialized triggers like Context updates or key changes can also cause it. (সাধারণত একটি React কম্পোনেন্টের state, props, অথবা parent পরিবর্তন হলে এটি রি-রেন্ডার হয়, তবে Context update বা key পরিবর্তনের মতো কিছু বিশেষ কারণেও এটি হতে পারে।)

import { useState } from "react";

export const ReRenderExample = () => {
  const [count, setCount] = useState(0);

  return (
    <div>

m3h3d1ha2an

<?php
<!-- input from anywhere (browser, mobile app, postman, etc) -->
<!-- /api/v1/blogs/42/comments/7?sort=desc&limit=5&include=author,tags -->

<!-- output -->
 <!-- {
  "full_url": "/api/v1/blogs/42/comments/7?sort=desc&limit=5&include=author,tags",
  "path_segments": ["api", "v1", "blogs", "42", "comments", "7"],
  "resource": "blogs",

m3h3d1ha2an

নিশ্চয়! যেহেতু আপনি PHP এবং REST API style URL handling নিয়ে কাজ করছেন, আমি আপনাকে ৫টি প্র্যাকটিস টাস্ক দিচ্ছি যা real-world API parsing ও PHP array/json handling-এ সাহায্য করবে।

---

1. Dynamic Resource Extraction

Task: একটি URL string নিয়ে লিখুন যে function:

• সব resource এবং sub-resource কে dynamically array আকারে বের করবে।

m3h3d1ha2an

ইসলামিক বাংলা বইসমুহ - পরামর্শেঃ মনসুর আহমেদ from Dawahwise Bangla

• ১. যাদের দুআ আল্লাহ ফিরিয়ে দেন না - লিখেছেনঃ ইমাম জালালুদ্দীন সুয়ুতী রাহি - অনুবাদঃ হাফিজ আহমদ নাঈম
• ২. সফওয়াতুত তাফাসীর - লিখেছেনঃ শাইখ মুহাম্মাদ আলী আস সাবুনী রহ.
• ৩. হাদীস-শাস্ত্রের পারিভাষিক জ্ঞান - লিখেছেনঃ শায়খ আব্দুল হামিদ ফাইযী আল-মাদানী
• [৪. হাদীস অধ্যয়নের মূলনীতি - লিখেছেনঃ মাওলানা আবুল ফাতাহ মুহা. ইয়াহইয়া](https://www.rokomari.com/book/98310/%E0%A6%B9%E0%A6%BE%E0%A6%A6%E0%A7%80%E0%A6%B8-%E0%A6%85%E0%A6%A7%E0%A7%8D%E0%A6%AF%E0%A7%9F%E0%A6%A8%E0

m3h3d1ha2an

1. Make Sure Everything Is Up to Date

git switch dev
git pull origin dev
git switch main
git pull origin main

2. Rebase dev onto main

This puts all your dev commits “on top of” main, making the history linear and avoiding merge commits.

m3h3d1ha2an

A Modern Way to Create a Dialog or Modal Without JavaScript (Pure HTML and CSS Only) in 2025

This example demonstrates how to build a fully functional dialog/modal using only HTML and CSS.

HTML Structure

<!-- HTML Structure for the Dialog -->
<input type="checkbox" id="dialog-toggle" class="hidden">
<label for="dialog-toggle" class="dialog-open">Open</label>
<div class="dialog-backdrop">

m3h3d1ha2an

Problem

browser-external:events:9 Module "events" has been externalized for browser compatibility. Cannot access "events.EventEmitter" in client code. See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.

Solution:

i used this package to fix the problem: vite-plugin-node-polyfills

pnpm install --save-dev vite-plugin-node-polyfills

Usage

m3h3d1ha2an

Setup Postgresql

run postgresql with systemctl

Install postgres

latest

sudo pacman -S postgresql

specific version

find version & build from source

m3h3d1ha2an

Problem: Property 'user' does not exist on type 'Request<ParamsDictionary, any, any, ParsedQs, Record<string, any>>'

When working with Express and jsonwebtoken, it's better to use res.locals to store user-related data rather than modifying the req object directly. This approach adheres to best practices and avoids potential issues with modifying the req object.

Here’s why:

1. Separation of Concerns: res.locals is designed for passing data to subsequent middleware or templates. It keeps the request object clean and unmodified.
2. Middleware-Safe: Using res.locals ensures that the data is available to other middleware without interfering with the original request object.

Instead of: