DEV Community

20 Killer JavaScript One-Liners That’ll Save You Hours of Coding 🤯🔥

Ram Maheshwari ♾️ on January 27, 2023

Take your JavaScript skills to the next level with these essential one-liners that will also save you hours of coding 🚀 1) Find the ma...

Read full post

Peter Franken • Jan 27 '23 • Edited

Careful, JS is effing weird:

!isNaN(parseFloat('Infinity')) // true
typeof NaN === 'number' // true (lol)
typeof null === 'object' // true
typeof Math === 'object' // true
typeof MyClass === 'function' // true
typeof new Date() === 'object' // true

There's more where that came from, but the gist of it is that whenever JS claims something is an object, function, or numerical value it's probably lying or not telling the whole story. Mistakes with JS types can lead to some very nasty bugs, so always make sure you know what is actually going on with your code!

I highly recommend reading up on how prototypes work, or at the very least check out this this MDN page on typeof's various gotcha's: developer.mozilla.org/en-US/docs/W...

Mahmoud Harmouch • Jan 28 '23 • Edited

That's just the tip of the iceberg:

NaN == NaN // false (Lol), so it seems like these NaNs are two different instances of a NaN object?
NaN instanceof Number // false, even though it is part of IEEE 754 numeric standard.
NaN == Number.NaN // false (lol), two different NaNs in JS? Probably like the first case (two different instances).
parseInt(NaN) // NaN (lol)
Infinity == Infinity // true (lol), like how?

Rafael Pereira • Jan 28 '23

You're treating NaN as a constant, which is not. Makes a lot of sense once you understand what NaN is. When you do an operation that results in NaN, its failure is not exactly the same as the other. Imagine doing an operation manually and you'll understand that it's never equals the other and there are more ways to reach that result, making it always different. This blog post is good to know more: ntgard.medium.com/why-nan-nan-3d41...

Infinity is not reverse NaN, they are pretty different. Infinity behaves as a property (or constant), which is the highest number (or lowest in case of negative infinity).

Infinity > Infinity // false

Mahmoud Harmouch • Jan 28 '23 • Edited

You're treating NaN as a constant, which is not.

I am literally using instanceof, which means not a constant, I guess?

Makes a lot of sense once you understand what NaN is.

When you do an operation that results in NaN, its failure is not exactly the same as the other. Imagine doing an operation manually and you'll understand that it's never equals the other and there are more ways to reach that result, making it always different.

Why are you explaining it like it is magic?

Infinity is not reverse NaN, they are pretty different.

Of course. But, I mean does it make more sense Infinity == Infinity is true and NaN == NaN is not?

Rafael Pereira • Jan 28 '23 • Edited

I am literally using instanceof, which means not a constant, I guess?

Great, then why the comparison? Just because a instanceof can be equal to the other doesn't mean all of them are equal, right?

Why are explaining it like it is magic?

I tried to explain because I thought it would help. A lot of times when I was learning JavaScript and came into something like this, an explanation which was not complex as say IEEE754 really helped me. So if it sounded condescending I'm sorry, it was not my intention.

Of course. But, I mean does it make more sense Infinity == Infinity is true and NaN == NaN is not?

At first yes, for sure. That's why it's important to see how they got to this point when they were developing the language. It's not a bug if it's intentional and I was very surprised with most of them to be intentional when I was learning. I mean, it's part of the process to start liking it, otherwise people tend to be stuck in "this language is trash because of this", you know? At least happened to me.

Mahmoud Harmouch • Jan 28 '23

A lot of times when I was learning JavaScript and came into something like this, an explanation which was not complex as say IEEE754 really helped me.

But, my concern is that there is a NaN object under the Number type (Number.NaN) even though NaN is NOT a number - I think the reason for this is that NaN is part of the IEEE 754 values which means all Number values including NaN. So, the thing that is confusing is the naming of these variables. Same thing for Infinity which is not actually the usual mathematical infinity, but rather a const (max value):

parseFloat("Infinity") === Infinity // true
parseFloat("NaN") === NaN // false

At first yes, for sure. That's why it's important to see how they got to this point when they were developing the language. It's not a bug if it's intentional and I was very surprised with most of them to be intentional when I was learning. I mean, it's part of the process to start liking it, otherwise people tend to be stuck in "this language is trash because of this", you know? At least happened to me.

Yeah, i see.

Thank you for sharing your knowledge and experience.

codingjlu • Jan 28 '23

IMO infinity is not a number.

Peter Franken • Jan 28 '23

Agreed, which makes it all the more useful to know that it's classified as one in JS anyway (and in fact by most other software and runtimes too, due to the IEEE 754 standard for floating-point arithmetic).

The isFinite global function (spec, MDN) might come in handy next time you need to validate a numerical type.

script-neutron • Jan 28 '23

Yes

Kitanga Nday • Jan 29 '23

Infinity is a number in math. I think it's set this way for internal reasons, but outside of programming infinity is a number

Peter Franken • Jan 29 '23

At the risk of sounding super pedantic, it would be more accurate to say infinity represents a number (a quantity) rather than actually being one itself. Unlike maths' infinity which can actually represent different measures, JS' version is essentially just an "out of bounds" indicator (x+n) within our "fake" digital/binary arithmetic and therefore only infinite on a philosophical level.

Funny when you realise that JS' infinity is actually, at its most basic level, a very much finite amount of ones and zeroes.

Josef Held • Jan 28 '23

Well, in JS it is a number.
maybe calling it Infinity was a poor choice 😉

Ram Maheshwari ♾️ • Jan 28 '23

Thanks for sharing 🙌

Uploadcare • Jan 31 '23

The fact that NaN is a number is totally fine and is not related to the JS. It's due to IEEE-754.

However, isNaN is broken, that's true.

What is NaN in JavaScript?

Uploadcare ・ Jan 25 ・ 7 min read

#javascript #webdev #beginners #programming

Peter Franken • Jan 31 '23

That is a very solid and comprehensive article! Whilst not new knowledge to me, I believe people who might not be as familiar with this subject should have no problems following along!

Thanks for sharing it here

Mat Borowiak • Feb 2 '23

Math is a global object
Class is a function, there are no classes in JavaScript, it is a syntatic sugar over native functions, which are virtualised through objects.
See what Date constructor returns.

What you are implying is ridiculous to anyone who knows JavaScript. You clearly don't, so I am not sure what makes you confident to throw falsy claims about JS "lying". You didn't even check the language spec, and have no clue how this works.

developer.mozilla.org/en-US/docs/W...
developer.mozilla.org/en-US/docs/W...
developer.mozilla.org/en-US/docs/W...

Peter Franken • Feb 3 '23 • Edited

You misunderstand. I merely listed some common pitfalls that newcomers often seem to run into, and provided a link to further details.

What a hateful and abusive response. Completely uncalled for and gained you nothing.
I wish you a more joyful and happy day tomorrow.

Kitanga Nday • Jan 29 '23

Second I saw that isNaN example I knew I had to check comments. IsNaN is very annoying to work with.

Bitcreep • Feb 1 '23

Everything besides null , undefined , strings, numbers, boolean, and symbols are objects in javascript.

jimmonte • Mar 6 '23

There are also BigInts

Shubham Tiwari • Jan 27 '23

21) Delete a specific item from an array -
arr.splice(arr.indexOf(item_to_delete),1)

Example -
let arr = ["A","B","C","D","E"];

arr.splice(arr.indexOf("C"),1)

console.log(arr)//[ 'A', 'B', 'D', 'E' ]

Jon Randy 🎖️ • Jan 28 '23 • Edited

Or:

let arr = ["A","B","C","D","E"]
arr = Object.values(({[arr.indexOf('C')]:arr,...arr}=arr,arr))
console.log(arr)  //[ 'A', 'B', 'D', 'E' ]

🤣🤣🤣

Gold star to the first person to fully explain how this works

Jon Randy 🎖️ • Jan 28 '23

Makes you sound like a pirate reading that second line of code! Arrrrrr!

Shubham Tiwari • Jan 28 '23

Well this is the best method i found to delete an element inside DOM as a Jr. Developer 😂😂
If it is wrong correct it 🥶

𒎏Wii 🏳️‍⚧️ • Jan 30 '23

Oh boy, this is gonna be fun. First of all, re-formatting the code a bit will make it a lot more readable:

Object.values(
  (
    {
      [arr.indexOf('C')]:arr,
      ...arr
    } = arr,
    arr
  )
)

Starting from the outside, Object.values does what it says on the tin and returns the values of the object, so it's safe to assume whatever happens on the inside will return an object mapping some values to the array items except for the one to be deleted.

The inner pair of braces is a bit weird. I haven't checked this with the documentation, but from the looks of it, the form (exp_1, expr_2) will evaluate two expressions and return only the latter, so this block could be somewhat reshaped into something along these lines:

    {
      [arr.indexOf('C')]:arr,
      ...arr
    } = arr
    return arr

if it was a function. So the code applies some de-structuring magic to the array, then hands it back to Object.values as mentioned above.

Now, for the de-structuring part, here's where the real magic happens.

The first access of arr inside square braces is just accessing the array for reading; it gets the index of the element to be deleted. The second two occurrences of arr can be thought of as "writing" access, as in these are making changes to the variable.

Looking at the components here:

({...foo} = bar) is a weirder way of writing foo = {...bar} but using destructuring. So what's happening there, on its own, is arr = {...arr}, meaning we get an array-like object copy of arr.

({[0]: foo} = [1, 2, 3]) is equivalent to foo = [1, 2, 3][0]

At this point, I'm still struggling to wrap my head around what actually happens here, but with a bit of testing, it looks like the rhs of the de-structuring assignment doesn't have to be the same variable, which makes for a much simpler example:

({[0]: arr, ...arr} = [1, 2, 3], arr)

This somehow results in the object {1: 2, 2: 3}.

After some more testing, it looks like the first arr in this expression can be any other variable:

({0: _, ...arr} = [1, 2, 3], arr)

Which now makes it a lot more obvious what's going on. The key 0 (in my example) is being de-structured into some throw-away variable, then the remaining key-value pairs are de-structured into arr. In the original code, this "throw-away" variable just happens to also be arr to save up on a let and to make the code a bit more confusing.

So, what ultimately happens is:

The index of the value to delete is calculated
The array is de-structured into a throw-away variable (key from 1.) and into arr (other keys)
arr is passed into Object.values, returning all values of the array except the one to be deleted in the form of a new array.

There you go :)

Jon Randy 🎖️ • Jan 30 '23

⭐

Shubham Tiwari • Jan 28 '23

It deletes an element lol 😂😂

Rudy Nappée • Jan 27 '23

Or arr = arr.filter(i => i !== "C")

Shubham Tiwari • Jan 28 '23

But i think using filter method to delete an element is heavy process as filter method returns a new array , suppose you are performing this action on 1000 Dom elements, it means if you remove 1 element using filter, other 999 element will rerender
On the other hand using splice method will remove the element from the original array directly

Marcelo Martínez • Jan 28 '23

Talking about React, the other 999 elements won´t rerender because it keep track of them with a key and knows they haven´t changed.

Also, Reacts uses the Object.is(x, y) method to know when the state changed, and if you remove an array element using splice, React won´t rerender because it still is the reference to the same array even tho you modified it.

Shubham Tiwari • Jan 28 '23

And for the Vanilla javascript?
Btw I use Event Propagation to remove Elements from DOM in Vanilla javascript

Rudy Nappée • Jan 28 '23

What do you mean by rerender ?

Shubham Tiwari • Jan 28 '23

Like once in a project i mapped the Array item with HTML UI using method,
Then delete element with button click using filter method, What it was doing is refreshing the entire list of HTML element, like there is a update Dom method which sets the innerHTML of the list with the updated array
So it was doing a heavy operation with that filter array approach
Then i used the Event Propagation and find the element using closest() method of DOM, when we click on delete button of an element, it will find the closest parent element which holds that delete button and other Things, and then deleting that parent element using remove() method

Rudy Nappée • Jan 28 '23

Actually with React you shouldn't mutate your state. If your keys are consistent it will not rerender your other elements. With filter, the objects identities doesn't change, only the array identity (it returns a new array containing the same objects).

Shubham Tiwari • Jan 28 '23

Also if we splice the state of useState and then update the state with the spliced version using setState, will it make a difference?

Rudy Nappée • Jan 28 '23

Don't mutate your state in React !
stackoverflow.com/questions/551785...

Shubham Tiwari • Jan 28 '23

Ohk thanks for this

Ram Maheshwari ♾️ • Jan 28 '23

Looks great, Thanks for sharing 🙌

Mahmoud Harmouch • Jan 28 '23 • Edited

Thanks for sharing. I have added the python equivalent (assuming an array is a list in python for simplicity):

1) Find the max value in an array:

max(array)

2) Remove duplicates from an array:

[*set(array)]

3) Generate a random number between 1 and 100:

import random; random.randint(1, 100) # one-liner, LOL.

4) Check if a string is a valid number:

Your method is not correct:

!isNaN(parseFloat("123.asd")) // true

Probably you meant "Check if a string contains a number"?

python equivalent:

string.lstrip('-').replace('.','',1).isdigit()

5) Get the current date and time:

from datetime import datetime; datetime.utcnow() # datetime.datetime(2023, 1, 28, 8, 24, 41, 221834)

6) Check if a variable is an array:

type(array) is list

7) Check if a variable is an object:

issubclass(variable , object)

8) Convert an array to a string:

",".join(array)

9) Check if a variable is a function:

import inspect; inspect.isfunction(variable)

10) Convert an object to an array:

Depends on the type of the object. For example dict:

[*dict_object.items())]

11) Count the occurrences of an element in an array:

array.count(element)

12) Create a new object with a dynamic key and value:

{ key: value}

13) Check if a string is a palindrome:

string == string[::-1]

14) Get the the sum of all the numbers in an array

sum(array)

from functools import reduce, operator; reduce(operator.add, array)

15) Get the current timestamp:

from datetime import datetime; datetime.timestamp(datetime.now())

16) Check if a variable is null (None in python):

not variable

17) Check if a variable is undefined:

'variable' in vars() or 'variable' in globals()

18) Find the minimum value in an array

min(array)

19) Check if an array is empty:

not array

20) Create a new array with a specified range of numbers:

[* range(n)]

Ram Maheshwari ♾️ • Jan 28 '23

This is amazing, Thanks a lot for sharing 🔥🙌

rjbudzynski • Jan 28 '23

19 can be simplified tonot array.

6 to type(array) is list

BTW in a python context array usually refers to numpy array rather than list.

Mahmoud Harmouch • Jan 28 '23

Thanks for the heads up. Fixed!

Posandu • Jan 27 '23

Shorter version for 20

[...Array(n).keys()]

Ram Maheshwari ♾️ • Jan 28 '23

That's helpful, Thanks for sharing 🙌

Pulkit Singh • Jan 27 '23

great. isn't 2, 14 and 18 the same?

Ram Maheshwari ♾️ • Jan 28 '23

Thanks for the update, I just fixed that 🙌

codingjlu • Jan 28 '23

I love how you've included [...new Set(array)] 3 times. By the way, isNaN automatically tries to parse the string into a number, and returns false when failing, so no need to wrap the string in parseFloat.

Ram Maheshwari ♾️ • Jan 28 '23

That's helpful, Thanks for sharing 🙌

Jon Randy 🎖️ • Jan 28 '23 • Edited

8) Convert an array to a string:

'' + array

13) Check if a string is a palindrome:

string === [...string].reverse().join``

Using split('') will not work with some strings - try "🤔😈".

Ram Maheshwari ♾️ • Jan 28 '23

Thanks for sharing 🙌

James Wilkinson • Jan 27 '23

ChatGPT will be loving all this

Ram Maheshwari ♾️ • Jan 28 '23

Yeah 🙌

Humbel Micha • Jan 27 '23

Love it :) Isn't 2, 14 and 18 exactly the same?

Red Ochsenbein (he/him) • Jan 27 '23

And ironic...

Ram Maheshwari ♾️ • Jan 28 '23

Thanks for the update, I just fixed that 🙌

Moisés Alcocer • Jan 28 '23

Alternatively to the tip number 8, when you want to have something as 1,2,3,4 (array elements separated by commas in a string) you can simply use:
arr.toString();

Ram Maheshwari ♾️ • Jan 29 '23

That's very helpful, Thanks for sharing 🙌

Benjamin • Jan 27 '23

[...new Set(array)] is duplicated in your post 😉

Ram Maheshwari ♾️ • Jan 28 '23

Thanks for the update, I just fixed that 🙌

Kitanga Nday • Jan 29 '23

array.length === 0 can be shortened to !array.length

Ram Maheshwari ♾️ • Jan 29 '23

That's very helpful, Thanks for sharing 🙌

Lotfi Jebali • Jan 27 '23

These are good practices
Thank you for sharing

Ram Maheshwari ♾️ • Jan 28 '23

Sounds great, Thank you 🙌

Brian Aponte • Jan 28 '23

Great article. Thanks Ram!

Ram Maheshwari ♾️ • Jan 28 '23

Sounds great, Thanks a lot ❤️🙌

Jared Odulio • Jan 29 '23

Thanks for sharing!

Ram Maheshwari ♾️ • Jan 29 '23

No problem 🙌

Karl Krasnowsky • Jan 28 '23

13) Check if a string is a palindrome:

Well there's something I've been looking for. 😆

Ram Maheshwari ♾️ • Jan 29 '23

Sounds good 😅

Kumar Kalyan • Jan 29 '23

nice article @rammcodes

Ram Maheshwari ♾️ • Jan 29 '23

Thank You 🙌

iikitty • Jan 31 '23

4) Check if a string is a valid number:

!isNaN(parseFloat(string))

This one is not working properly

const string = '1234.5678';
!isNaN(parseFloat(string)); // true
!isNaN(string);             // true

const string = '1234あ5678';
!isNaN(parseFloat(string)); // true
!isNaN(string);             // false

const string = '1234.5678.9';
!isNaN(parseFloat(string)); // true
!isNaN(string);             // false

iikitty • Jan 31 '23

This one works better & properly.

!isNaN(+string)

jimmonte • Mar 6 '23

Starting at the left end of the string after skipping any whitespace characters, parseFloat() only returns NaN if the first characters do not form a float number. The function stops parsing at the character that ends the number and returns the number found to that point.

Jakub T. Jankiewicz • Feb 25 '23 • Edited

You don't need parseFloat with isNaN, to check if value is a number. it will be converted to number before the check:

!isNaN('100') == true
!isNaN('hello') == false

There is Number.isNaN that don't do the conversion.

FiftyP • Jan 30 '23

Why does #3 seem 'smelly' to me?

"Generate a random number between 1 and 100:
Math.floor(Math.random() * 100) + 1"

Math.random() => 0 to 1 (NOT including 1) => [0, 1)
Math.random()*100. => 0 to 100 (NOT including 100) => [0, 100)
Math.floor(Math.random()*100) => int(0 to 100) (NOT including 100) => [0, 100)
Math.floor(Math.random()*100)+1 => int(1 to 101) (NOT including 101) => [1, 101)

so, the Math.floor(Math.random()*100)+1 CAN include 100, so is NOT '1 to 100 (not including 100)', which would be expected from all the other descriptions of 'A to B' which DON'T include the upper bound.
IMO, the description "between" is (1, 100), but the functions used seem to be [a,b), so the user might also expect [1,100), but they actually get [1,100] - or [1,101) since they're only integers.

FiftyP • Jan 30 '23

found = false; count = 0; while (!found) { const value = Math.floor(Math.random() * 100) + 1; found = value === 100; count++; } 197

João Eurico "Bokomoko" Lima • Jan 29 '23 • Edited

20 also could be done with

Array(n).fill(0).map((_,i)=>i)

Jørn André Myrland • Feb 1 '23

Hey, you forgot this one:

!!~text.indexOf(query)

I use this one all the time.

Mahesh Bandara Wijerathna • Jan 29 '23

This whole article screams "I AM A JS BEGINNER". Most of these snippets will destroy your logic in specific scenarios. You should edit this.

gaoryrt • Jan 30 '23

20) Create a new array with a specified range of numbers:

[...Array(n).keys()]

Wade Zimmerman • Jan 29 '23 • Edited

Number 7 is wrong because arrays and null have a type of object. This is why typescript was invented.

typeof null // object
typeof {} // object
typeof [] // object

Chinmay Joshi • Jan 30 '23 • Edited

How can you forget the most valuable code while debugging - console.log("asdasdasd");

Volkan Alkılıç • Jan 28 '23 • Edited

Thank you ChatGPT for 20 useless tips that i already know.

Ram Maheshwari ♾️ • Jan 29 '23

🙌

zeeh1975 • Jan 30 '23

I like 20, very clever!

Matvey Romanov • Jan 31 '23

Thanks a lot :)

Jon Randy 🎖️ • Feb 1 '23

Somewhat weirdly, this post appears to have changed authors? 🤔 @thepracticaldev

Ram Maheshwari ♾️ • Feb 1 '23 • Edited

Yeah, I don't know how it got removed from my account and got transferred into this account @thepracticaldev , maybe some bug?

flyingCrp • Feb 2 '23

Ivan Karabadzhak • Jan 29 '23

I like your efforts. I think each JS developer should know those. But, be careful with isNaN function.