惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

IT之家
IT之家
博客园_首页
S
SegmentFault 最新的问题
罗磊的独立博客
博客园 - 【当耐特】
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
阮一峰的网络日志
阮一峰的网络日志
D
Docker
雷峰网
雷峰网
Google DeepMind News
Google DeepMind News
博客园 - 司徒正美
V
V2EX
大猫的无限游戏
大猫的无限游戏
V
Visual Studio Blog
腾讯CDC
宝玉的分享
宝玉的分享
酷 壳 – CoolShell
酷 壳 – CoolShell
人人都是产品经理
人人都是产品经理
T
Tailwind CSS Blog
Vercel News
Vercel News
H
Help Net Security
博客园 - Franky
D
DataBreaches.Net
aimingoo的专栏
aimingoo的专栏

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Understanding 'this' in JavaScript
Swarnali Roy · 2026-05-14 · via DEV Community
Cover image for Understanding 'this' in JavaScript

Swarnali Roy

One JavaScript concept that confused me for a long time is the concept of this. At first, it looks simple. But while using inside a function, the behavior changes based on how the function is called.

It works differently in :

  • Normal function
  • Object Method
  • Arrow Function

Normal Function

In a normal function, this usually refers to the global object or undefined in strict mode.
Example:

function test() {
  console.log(this);
}

Enter fullscreen mode Exit fullscreen mode

The output will show window in a non-strict mode and undefined in a strict mode.

Object Method

When a function is called as a method of an object, the this keyword refers to the object that is calling the method.
Example:

const user = {
  name: "Swarnali",
  Name() {
    console.log(this.name);
  }
};
user.Name();

//Output : Swarnali

Enter fullscreen mode Exit fullscreen mode

In user.Name(), the object (user) before the dot(.) becomes the value of this inside the function. That is why this.name accesses user.name. This allows methods to work with the object’s own properties dynamically. However, if the function is separated from the object and called independently, it loses that connection, and this no longer refers to the original object.

Arrow Function

Arrow functions behave differently from normal functions because they do not create their own this context. Instead, they inherit this from the surrounding scope where the arrow function was originally defined. This is called lexical scoping.
Example:

const user = {
  name: "Swarnali",
  Name: () => {
    console.log(this.name);
  }
};

user.Name();

//Output: undefined

Enter fullscreen mode Exit fullscreen mode

In this example, Name is defined using an arrow function inside the user object. As a result, this.name will not access "Swarnali" and may return undefined depending on the environment. This is why arrow functions are generally not recommended as object methods when you need to access the object’s own properties using this.

How to determine when to use which this?

One easy method to determine whether to use a normal function or an arrow function would be the question, "Do I need my own this?"
In cases where the function must access variables from the object that called it, the choice would be to write a normal function since they have their own this value. This is common for object methods and class methods.
When a function requires a this value passed to it through the surrounding scope, then write an arrow function. Arrow functions are especially useful in callbacks, nested functions, array methods like map() or filter(), and asynchronous operations such as setTimeout(), where preserving the parent context is important.

Do you face this confusion as well?