FediScanner

#react

← Back

RECRUITING! Are any of my network on here (or in yours!) Native developers, but like, as your main? ie, not I *could* do that but like, that's my bag and I've done it 5+ years? 6 mth contract incoming from one of my ongoing political clients. The focus will be on modernising and strengthening the existing application they've built vs building new features. It's pretty important stuff so I'm looking for strong senior vs it's in my wheelhouse.

Show Original PostReport

Blockchain.com is hiring Senior React Native Engineer

🔧 #react #reactnative #java #javascript #kotlin #swift #typescript #android #ios #cicd #seniorengineer
🌎 Buenos Aires, Argentina
⏰ Full-time
🏢 Blockchain.com

Job details jobsfordevelopers.com/jobs/sen
#jobalert #jobsearch #hiring

Show Original PostReport

Почему архитектура важнее выбора стейт-менеджера в React

Почему архитектура важнее выбора стейт-менеджера в React Когда я только начинал свой путь разработчика мне было интересно изучать новые технологии. Учил все подряд. Все знал. Но что лучше или хуже и уже тем более почему — сказать не мог. Именно об этом — как писать код правильно — я собираюсь сейчас рассказать. И буду это делать через призму выбора стейт-менеджера в React.

habr.com/ru/articles/1089216/

#react #architecture #state_management #mobx #effector #zustand #rxjs #jotai #tanstack_query #архитектура_фронтенда

Show Original PostReport

TanStack Start vá lỗ hổng XSS nghiêm trọng CVE-2026-102989 (CVSS 9.3): nâng cấp ngay hôm nay

Trả lời nhanh: Ngày 30/9/2026, TanStack phát hành bản vá cho lỗ hổng reflected XSS nghiêm trọng trong TanStack Start (mã định danh CVE-2026-102989, điểm CVSS 9.3). Kẻ tấn công chỉ cần gửi cho bạn một đường link là có thể khiến trình duyệt chạy mã JavaScript độc hại dưới chính tên miền website của bạn — không cần tài khoản, không cần quyền truy cập mã nguồn. Nếu dự án của bạn dùng TanStack Start […]

linhfishcr7.wordpress.com/2026

Show Original PostReport

useRef is a React Hook that is used to store a value that persists between renders without causing the component to re-render when the value changes.

It is also commonly used to access and interact with DOM elements directly.

Syntax


const reference = useRef(initialValue);

For example:

const count = useRef(0);

What Does useRef Return?


useRef() returns an object containing a property called current.

const count = useRef(0);

console.log(count);

The result is similar to:

{
current: 0
}

The value can be accessed or changed using:

count.current

For example:

count.current = count.current + 1;

Why Do We Use useRef?


useRef is commonly used for:

  1. Accessing DOM elements
  2. Storing values between renders
  3. Keeping a previous value
  4. Storing values without causing a re-render


Example 1: Accessing a DOM Element


One of the most common uses of useRef is focusing an input element.

import { useRef } from "react";

function App() {

const inputRef = useRef();

function focusInput() {
inputRef.current.focus();
}

return (
<div>
<input ref={inputRef} />

<button onClick={focusInput}>
Focus Input
</button>
</div>
);
}

export default App;

How does it work?


First, we create a ref:

const inputRef = useRef();

Then we attach it to the input:

<input ref={inputRef} />

React stores the input DOM element inside:

inputRef.current

When the button is clicked:

inputRef.current.focus();

the input receives focus.

Example 2: useRef Does Not Cause Re-render


Consider:

const count = useRef(0);

We can change the value:

count.current = count.current + 1;

But changing count.current does not cause the component to re-render.

This is an important difference between useRef and useState.

useStateuseRefStores stateStores a mutable referenceUpdating state causes re-renderUpdating .current does not cause re-renderUses a setter functionUses .currentUsed when UI needs to updateUseful when UI does not need to update

useRef for Storing Previous Values


useRef can also be used to remember a value from the previous render.

import { useEffect, useRef, useState } from "react";

function App() {

const [name, setName] = useState("Maha");
const previousName = useRef("");

useEffect(() => {
previousName.current = name;
}, [name]);

return (
<div>
<h2>Current Name: {name}</h2>
<h2>Previous Name: {previousName.current}</h2>

<button onClick={() => setName("Lakshmi")}>
Change Name
</button>
</div>
);
}

export default App;

Here, previousName.current can store a value that persists between renders.

useRef vs useState


Suppose we have:

const [count, setCount] = useState(0);

When we write:

setCount(count + 1);

React updates the state and re-renders the component.

But with:

const count = useRef(0);

when we write:

count.current = count.current + 1;

the value changes, but React does not re-render the component just because the ref changed.

Simple Flow

useState


State changes
↓
React re-renders
↓
UI updates

useRef


ref.current changes
↓
No automatic re-render
↓
Component UI does not automatically update

Conclusion


useRef is useful when a value needs to persist between renders without triggering a re-render. It is especially useful for accessing DOM elements, storing previous values, and keeping mutable values that do not directly control the UI.#react #webdev #software #coding #development #engineering #inclusive #community
useRef Hook in React

Show Original PostReport

Capacitor: от веба к мобильным приложениям. Часть 5. Микрофронтенды в Capacitor

Ого, да это же следующая статья цикла про Capacitor. В ней мы рассмотрим нюансы реализации микрофронтендов в Capacitor приложении,а также разбирем схему, в которой команды могут выпускать MFE независимо и не ломать нативную часть приложения.

habr.com/ru/articles/1089150/

#capacitor #микрофронтенды #module_federation #react #typescript #гибридные_приложения #диплинки #otaобновления #мобильные_приложения #мобильная_разработка

Show Original PostReport