How Dot Notation Works with Numbers in JavaScript?

Have you ever seen something weird in JavaScript like this?

console.log(3.toString()); // SyntaxError!

If you’re wondering why this throws an error, but this works:

console.log((3).toString()); // "3"
console.log(3..toString());  // "3"

You’re not alone. Let’s break down why numbers and dot notation behave this way in JavaScript.

Dot Notation Basics

JavaScript lets us access methods and properties using a dot:

"hello".length;         // 5
[1, 2, 3].push(4);       // [1, 2, 3, 4]
(42).toString();         // "42"

But with plain numbers, you can run into a problem…

Why 3.toString() Fails

When JavaScript sees 3. followed by letters, it thinks you’re trying to write a floating point number like 3.14.

So when you type 3.toString(), the parser gets confused. It thinks you’re trying to write a number with a decimal part, not calling a method.

Three Ways to Fix It

1. Use Parentheses

(3).toString(); // "3"

2. Add a Second Dot

The first dot is the decimal point, the second is for the method:

3..toString(); // "3"

3. Use a Variable

const num = 3;
num.toString(); // "3"

So… Are Numbers Objects?

Not really. Numbers are primitive values. But when you try to use a method on them, JavaScript temporarily wraps them in a special object called a Number object, just long enough to access the method like toString() or toFixed().

Other Useful Number Methods

const score = 98.765;

console.log(score.toFixed(1));   // "98.8"
console.log(score.toPrecision(3)); // "98.8"
console.log((255).toString(16));   // "ff" (hex)

Conclusion

JavaScript’s dot notation works great — until numbers trip it up. Just remember: if you want to call a method on a number, wrap it in parentheses or use two dots. Under the hood, JavaScript treats primitives like objects just long enough to get the job done. Once you understand this little quirk, you’ll never be confused by 3..toString() again!