This question revisits closure - one of the most confusing concepts in JavaScript. Closure allows us to create a stateful function and such a function can access to the variable outside of its scope. In a nutshell, a closure can have access to the global variable (scope), father function scope and its own scope.

We have here, the only one correct answer, 3, 3, 3 and 3, 4, 5 because first we simply call the function a(). It works like a normal function and we have not seen anything so-called stateful yet. In the following code, we declare a variable x and it stores the value of function a(1), that is why we get 3. 4. 5 rather than 3, 3, 3.

This kind of gotcha gives me the feeling of static variable in PHP world.

We get true in the console. The tricky part is when we create an object from the constructor function Name but we DO NOT USE new keywork. That makes the variable a global one and get the value "Vuong". Remember that it is actually a property of the global object window (in the browser) or global in the nodejs.

We then get a.length ~ 5 and window.a.length ~ 5 which return 0. !0 returns true.

Imagine what would happen when we create the instance me with the new keywork. That is an interesting inquire!

The spread operator ...x might help us obtain the parameter in the function in the form of array. Yet, in Javascript the typeof array return "object" rather than "array". It is totally odd if you are coming from PHP.

That is said, we now have the length of the string object which returns 6. z.y() simply returns the length of the string 'freetut' (7).

Be aware that the function x() (in the form of function express or anonymous function (if you are coming from PHP) return -1 when being called and when converted to bool with Boolean(-1) return true instead of false. Noted that Boolean(0) return false.

The function js() can be automatically executed without calling it and known as IIFE (Immediately Invoked Function Expression). Noted the parameter x of the function js is actuallly passed with the value 3.

The value return of the function is y(s())), meaning calling three other functions y(), s() and j() because the function s() returns j().

j() returns 3^3 = 27 so that s() returns 27.

y(s()) means y(27) which returns 27*3 = 81.

Note that we can call declare function BEFORE the function is actually declared but not with expression function.

We have here an IIFE (Immediately Invoked Function Expression). It means we do not have to call it but it will be excuted automatically when declared. The flow is as: husband() returns wife()/2 and wife() returns tip*2.

We might think that tip = 100 because it is a global variable when declaring with var keyword. However, it is actually undefined because we also have var tip = 10 INSIDE the function. As the variable tip is hoisted with default value undefined, the final result would be D. We know that undefined returns NaN when we try to divide to 2 or multiple with 2.

If we do not re-declare var tip = 10; at the end of the function, we will definately get B.

JS is fun, right?

This challenge revises the ES6's feature regarding spread operator ... Spread operator is quite useful for retrieving parameter in function, to unite or combine object and array in JavaScript. PHP also has this feature.

In the variable edu, we use ...js (spread operator here) to combine both objects into one. It works in the same way with array.

Then we declare another variable named newbie. IMPORTANT note: By declaring the variable like that, both variables point to the SAME POSITION in the memory. We may have known something like $a = &$b in PHP, which let both varibles work in the same way. We might have known about pass by reference in the case.

Then we have 2 as edu.language is deleted. Both objects now have only two elements.

Now is time to think about coping an object in JS either shallow or deep one.

The buit-in method Object.assign(candidate, job) merges the two objects candidate and job into one object. Then the method Object.keys counts the number of key in the object.

Note that two methods get() and count() are defined as static, so they need to be called statically using Class.staticmethod() syntax. Then the final object get 5 elements.

Initially x is declared with the value 1. In the first IIFE function, there are two operations. First x becomes 2 and then 3.

In the second IIFE function, x = x + y then the current value is 5. In the second operation, it returns only 1 as it undergoes 5%2.

In the third and fouth IIFE functions, we get 2 x = x + x and then 4 x = x * x. It is more than simple.

This question illustrates the diffences between PHP and JavaScript when handling closure. In the first snippet, we declare a closure with the keyword use. Closure in PHP is simply an anonymous function and the data is passed to the function using the keyword use. Otherwise, it is called as lambda when we do not use the keyword use. You can check the result of the snippet here https://3v4l.org/PSeMY. PHP closure only accepts the value of the variable BEFORE the closure is defined, no matter where it is called. As such, $var is 10 rather than 15.

On the contrary, JavaScript treats the variable a bit different when it is passed to anonymous function. We do not have to use the keyword use here to pass variable to the closure. The variable x in the second snippet is updated before the closure is called, then we get 26.

Note that in PHP 7.4, we have arrow function and we then do not have to use the keyword use to pass the variable to function. Another way to call a global ariable inside a function in PHP is to use the keyword global or employ the built-in GLOBAL variable $GLOBALS.

Technically, x and y have the same value. Both are empty objects. However, we do not use the value to compare objects.

z is x are two objects referring to the same memory position. In JavaScript, array and object are passed by reference. x and z therefore return true when being compared.

Given that the function setTimeout() will be kept in the task queue before jumping back to stack, "hello" and "hi" will be printed first, then A is incorrect. That is also the case of the answers C and D.

No matter how many seconds you set to the setTimeout() function, it will run after synchronous code. So we will get "hello" first as it is put into the call stack first. Though the setTimeout() is then being put into the call stack, it will subsequently offload to web API (or Node API) and then being called when other synchronous codes are cleared. It means we then get "hi" and finally "world".

So B is the correct answer.

Credit: @kaitoubg (voz) for your suggestion regarding the timeout throttled by which I have decided to alter the question slightly. It will ensure that readers will not get confused as the previous code might bring out different results when tested on other browsers or environments. The main point of the question is about the discrepancy between the synchronous code and asynchronous code when using setTimeout..

String.prototype.someThing = function () {} is the common way to define a new built-in method for String. We can do the same thing with Array, Object or FunctionName where FunctionName is the function designed by ourself.

That is not challenging to realise that "string".lengthy() always returns hello. Yet, the tricky part lies in the delete object where we might think that this expression will entirely delete the object. That is not the case as delete is used to delete the property of the object only. It does not delete the object. Then we get hello rather than ReferenceError.

Note that if we declare object without let, const or var, we then have a global object. delete objectName then return true. Otherwise, it always returns false.

First we have an empty object x, then we add another property hi for x with x.__proto__.hi. Note this is equivalent to Object.prototype.hi = 10 and we are adding to the father object Object the property hi. It means every single object will inherit this propety. The property hi becomes a shared one. Say now we declare a new object such as let y = {}, y now has a propery hi inherited from the father Object. Put it simply x.__proto__ === Object.prototype returns true.

Then we overwrite the property hi with a new value 11. Last we have 11 + 1 = 12. x has one property and x.hi returns 11.

Updated (July 27th 2021). If you write Object.prototype.hi = 11; instead of Object.prototype.hi = ++x.hi; as written in the code above, then Object.keys(x) will return an empty array as Object.keys(object) only returns the property of the object itself, not the inherited ones. It means the final result will be 11 rather than 12. For some reason, the code ``Object.prototype.hi = ++x.hi;will create a property for the objectx` itself and then `Object.keys(x)` gives us the array `["hi"]`.

Yet, if you run console.log(x.hasOwnProperty("hi")) it still returns false. By the way, when you deliberately add a property for x such as x.test = "testing", then console.log(x.hasOwnProperty("test")) returns true.

This question examines how the delete operator works in JavaScript. In short, it does nothing when we write delete someObject or delete someArray. It nonetheless completely deletes and removes a property of an object when writing something like delete someObject.someProperty. In the case of array, when we write delete someArray[keyNumber], it only removes the value of the index, keep the index intact and the new value is now set to undefined. For that reason, in the code first snippet, we get (the length) 4 elements as in the original array but only 3 properties left in the object passed when the function object() is called, as in the second snippet.

The third snippet gives us 4 as declaring an object's propery to either null or undefined does not completely remove the property. The key is intact. So the length of the object is immutable.

For those who are familiar with PHP, we have unset($someArray[index]) that remove the array element, both key and value. When print_r the array, we might not see the key and value that have been unset. However, when we push (using array_push($someArray, $someValue)) a new element in that array, we might see that the previous key is still kept, but no value and not being displayed. That is something you should be aware of. Have a look at https://3v4l.org/7C3Nf

a and b returns false because they point to different memory location even though the values are the same. If you are coming from PHP world, then it will return true obviously when we compare either value or value + type. Check it out: https://3v4l.org/IjaOs.

In JavaScript, value is passed by reference in case of array and object. Hence in the second case, d is the copy of c but they both point to the same memory position. Everything changes in c will result in the change in d. In PHP, we might have $a = &$b;, working in the similar way.

The third one gives us a hint to copy an array in JavaScript using slice() method. Now we have f, which is the copy of e but they point to different memory locations, thus they have different "life". We get false accordingly when they are being compared.

The code snippet is quite tricky as it has a couple of different built-in methods handling object in JavaScript. For example, both Object.keys and Object.getOwnPropertyNames are used even thought they are quite similar except that the latter can return non-enumerable properties. You might want to have a look at this thoroughly written reference https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/getOwnPropertyNames

Object.values and Object.keys return the property value and property name of the object, respectively. That is nothing new. object.hasOwnProperty('propertyName') returns a boolean confirming whether a property exists or not.

We have flag true because Object.values(languages)[0][4].name returns feature, which is also the name of the property.

Then we have 4 << 4 in the if-else flow that returns the bitwise value, equivalent to 4*2^4 ~ 4*16 ~ 64.

We can use call(), apply() and bind() to apply a function to any object. At first sight, it seems that three functions do the same thing. Yet there are some situations where they are differently employed to handle respective contexts or solve particular problems.

Of the three, only bind() can be executed after binding. We can create a variable to store the result as helloRonaldo() in the code snippet above. apply() and call() will bind and execute the function at the same time. apply() hints us a ~ array where we need to pass an array as parameter. call() hints us c or comma where we pass parameters with a comma. You might want to have a look at this post https://stackoverflow.com/questions/15455009/javascript-call-apply-vs-bind

Note that window.window.window.score or window.score or simply score do the same thing. It points to the score() function in the global scope.

The correct anwser is D. The score() and getAge() functions are nothing special. The only tricky part is that this.age is incremented each time you call the funtion getAge();

bind() allows us to bind a function declared with any object. Here we bind score() and both ronaldo and messi.

In score() we pass three parameters year, tr and t in which both tr and t are function. They handle simple things as defined afterwards.

When we bind score() with ronaldo and messi, we pass three parameters as declared in the score() function wherein transform and title are functions.

Object.keys(obj) is almost identical to Object.getOwnPropertyNames(obj) except the fact that the latter returns any type of object's property regardless of enumerable. By default enumerable is true when creating object. Using Object.defineProperties or Object.defineProperty we can manually set this option to false.

As such the object person will get 3 usingObject.keys(obj)but 4 with Object.getOwnPropertyNames(obj). In short Object.keys(obj) only returns the property setting the enumerable as true.

When declaring a function inside another function, we are working with Closure in JavaScript. Note that if a function is declared as normal (rather than function expression), it is hoisted. We might see several id in the code snippet above but in fact, some of them does nothing.

The result of the code depending on the operator typeof id, which is function. So id in this operation is the id() function.

Object.create allows us to create an object which is based on another object. If we do not pass the second parameter - book2 in this case - the name property of the object bookCollection will be Name of the rose inherited from the book1. It means we can provide additional properties when declaring object with Object.create.

bookCollection has its own property name and another one inherited from book1. In this case its own property name will show up as it has higher priority. That is why we get 'Harry Potter'.

The two objects a and b are created using Object.create() operator. There is a bit of difference between them as a inherits from Object prototype but b is totally empty when we pass the null paramater. Yet hasOwnProperty('toString') always returns false neither a nor b given that toString() is not defined inside these objects. The method however is still available as it is inherited from Object prototype.

Both f1 and f2 return false. Note that we use object.hasOwnProperty('key') and ('key' in object) to check the availability of a key in an object. There is a bit difference between the two as the latter also returns the key inherited. You might want to have a look here: https://stackoverflow.com/questions/455338/how-do-i-check-if-an-object-has-a-key-in-javascript

Then typeof a.toString() returns string, which gives us 6 with the .length property.

If the syntax is odd to you, you might look for 'self-invoking function' and 'arrow function' in JavaScript.

We first declare a promise-based code with let and then call it. Given that setTimeout() is an asynchronous action, it will run last even the time is set to 0 in setTimeout(() => rs(4), 0);. Although Promise.resolve(console.log(3)) also returns a promise but it is a Microtasks, then it has a higher priority than Tasks as set by setTimeout(). You might want to have a look at this post https://jakearchibald.com/2015/tasks-microtasks-queues-and-schedules/.

In .then() we chain the result so that we have 4^4 in the first then() and 4*4 in the second then(). Note that return rs returns the original value.

Though we do not declare any paramater for the function f(), we pass setTimeout(()=>console.log("kiora"),0) when call it. We therefore get 'kiora' first.

Given that the variable promise returns a solved promise and it is called with the keyword await, JavaScript will 'pause' at this line console.log(await promise); till the result is resolved. That is why we get "done" at the next result.

Why we do not get "world" or "hello" at the second ? As JavaScript "pauses" at the line with await keyword, we cannot get "hello" as usual (note that whenever we call setTimeout(), this function will run last because it is an asynchronous task operator), whereas setTimeout(()=> console.log("world"), 0); should always run last.

Here we might see a bit of difference when employing await keyword before asynchronous operator (in this case, we use setTimeout() as an example) or when call the function/operator without it.

Both countryandfruit and fruitandcountry are self invoking functions. Both are declared with the keyword async, it means the code inside will run step by step. It helps us control the flow of data much more concise as compared to Promise-based operator or callback way.

The first function returns "Kiora: New Zealand Kiwi" and the second one ouputs "Hello: New Zealand Kiwi". We might think that the order will be the same but actually the order of the result is reversed because the function with await keyword will run step by step rather than in in parallel as Promise.all. It means fruitandcountry will run faster than countryandfruit.

You might want to have a look at the difference between the two at https://alligator.io/js/async-functions/

Object.entries returns an array consisting of both key and value from an object while Object.values retuns an array of the values of object and Object.keys gives us an array of keys of the object. As such, Object.entries(object) in the code snippet above gives us a nested array with just one element in which the values are put in another nested array like that [["month", ["July", "September", "January", "December"]]].

For that reason, Object.entries(this.object)[0][1].sort() will actually sort the value array and return a new order as "December" -> "January" -> "July" -> "September". Hence, when we get the element with the index given by [Object.values(this.object).length] we get January because [Object.values(this.object).length] give us 1 (the length of the array given by Object.values);

Comparing two arrays or two objects in JavaScript always return false because both are passed by reference, unlike primitive types such as string, number or boolean. That is why comparing [] and [] using either == or === returns false. The weird part is the !==!!!!! which is equivalent to !==, nothing special. So the flag is true.

In the expression function f(), we use arrow function here but and {} is a part of the function rather than an object. In case you want to return an object, you have to write as let f = () => ({}) or simply using normal way to define function. With the keyword return, we can easily catch the content of the function when using normal way to define function.

Thus, the typeof f() returns undefined rathern object. We then get the length 9 and the flag (true) becomes 'true' (a string, by using toString() function), which returns 3 with the property length. We finally get 13.

We have a self-invoking function with three parameters declared. Note that arguments inside a function returns an object consisting of the parameters of the function.

The key part here is that when we assign a value to that array (it is array-like, as mentioned above) (or any element), the function will use that value rather than the value from the parameter we pass to it when calling the function. Hence, c will be (typeof arguments).length; (6) rather than 3.

As c has a new value of 6, it is definitely less than 10, so we get the final result console.log(++c), which returns 7.

Note that arguments is not available on arrow functions. See more detailed here https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/arguments

From ES6 onwards, it is recommended to use ...restParameter given that it is a true array. It means you can manipulate the parameter with native JavaScript functions such as map, reduce or filter.

For PHP developer, we have func_get_args() in PHP that does the same thing, but it will not override the value passed. Check it by yourself at https://3v4l.org/dMfhW

We have a class named Calculator. When declaring a new instance of the object, we pass two parameters a and b. These two parameters have the same value but new Array(this.a).length is totally different from new Array(this.b).toString().length because the latter returns a string ",,,," meaning the length 4 while the former returns the length of an array and we therefore get 5.

For that reason getFlag() returns false. In getValue() we get typeof new Number(this.b); which returns object. That is a bit different from typeof b, which returns number.

The key point in this question involves the keyword this in JavaScript. We have a simple object that contains one method and one string property name.

First, it is important to write down is that let me = nz.callMe; and then call me() is totally different from directly calling nz.callMe(). If we assign a variable to a method delared inside an object, this in that method will behave differently (when we call the variable as a method and when dirrectly call that method). In particular, in the first case, this is the window object while in the second one, this inside the function still points to property name in the object nz. It means me() returns "Auckland" while nz.callMe returns "Kiwi".

Then result will return false and we get the final output value ${me()} ${she()}. Why she() is different from me()? You might easily guess that she still bind to the object nz rather than window object as in me().

The code snippet above is not a big challenge for you I guess. It simply gives you an example of this in different contexts when we declare an anonymous function inside a method of an object. The three first methods are common ways to handle this using this as second parameter in map(), by using bind(this) in forEach (or map()) or by that = thistechnique (you might see people use self = this rather than that= this).

The last method Me() will cause unexpected result because this.name does not bind to the object club. Note that you might get another result when testing the code on jsbin.com. On Chrome and Firefox, we get 0.

For further information, kindly have a look at http://speakingjs.com/es5/ch17.html#_pitfall_losing_this_when_extracting_a_method

... can be used in two ways in JavaScript (and PHP) as either spread operator or rest parameter. You might have to check the following article about the two. They are the same as three dots, but the way they are employed vary considerably between the two. https://javascript.info/rest-parameters-spread-operator

We see both spread operator and rest parameter in the code snippet above. First the parameter (...a) in the self-invoking function is of course a rest parameter while the constant c we see the spread operator. In the former case, it simply means that you can pass to the function as many parameter as you want. Note that the typeof a in this case is object even though it is a native array in JavaScript. (I means native array because you might think about array-like if we use arguments. Please have a look at the question 28 or this link https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/arguments).

Spread operator as in the constant c allows us to combine array. So ...a in the code above is rest parameter when it is used as function parameter but in this case it is the syntax of spread operator.

Finally, we get c with 5 elements (...a is a nested array, so the length is 1) but the first element has 10 child elements (when we pass to the function new Array(10)). The length of both then returns 15.

We have a function constructor Kiora (written with a capital letter, but that is optional) that can be used to create object, as the student object in the code above. In the function, we have two parameters with the second one is actually a rest parameter. The typeof operator is object but if we check with Array.isArray(array) it also returns true.

For that reason, Array.isArray(career) === true && typeof career === "object" returns true. Hence the return operator finally returns an object {}.

You might be surprised when console.log(student.name); outputs undefined given that the constructor function Kiora returns an object. Otherwise, we might simply get the value name.

Apologize that the code snippet is a bit longer than usual. But actually it is not really challenging as you might think. You can easily get the correct result after spending a little of time to debug.

First we declare a class that has two methods. The first method filter() will returns the first element of the array (of the propterty element) or simply returns hello depending on the type() method. We know that typeof of array will return object so the filter() method return this.element[0].name.

Try to make you feel confused, we then call the built-in filter() method. This native method returns a new array depending on the condition we pass to the call-back function. Note that !item.isdeveloped means false. It means we get Vietnam.

Finally we get New Zealand.length and Vietnam.length, which in total returns 18.

D is correct anwser. The order of the asynchronous code's output depends on the MicroTask or MacroTask. MicroTask has a higher priority. Note that the synchronous code always be executed before asynchronous code. So in essense, we have the order as follows:

  1) synchronous code
  2) microtask code (promise, queueMicrotask)
  3) macrotask code (setTimeout, setInterval)

Be awared that in Nodejs environment, we also have process.nextTick(callback) which has the highest priority but we dont have it in this code.

So, first callback in the setTimeout() will be executed last given that this is a MacroTask. That is why we got 1 last.

Second, the function abc() is called next. Then we have 8 printed out in the console first. As the next line of code inside that function is an asynchrnous code with the keyword "await", we then console.log(6) as Promise.resolve(4).then(console.log) is an asynchrnous code. That is why we got 6.

Now is the time for Promise.resolve(2), so we get 2. At this point, you might have some sort of confusion. What will happend if we do not pass the keyword "await" before Promise.resolve(2) ?

As we have await, the code will be blocked here. Then what? We get 0 and 4 not 3. Promise and queueMicrotask are both microtask and they are already to run before console.log(3). The reason is that microtask queue need to be emptied before any other codes can be called in the callstack.

In the next step, we get 3 and the last one is 1.

What would happend if we do not have the await keyword? Then the order of the output will be 8 - 3 - 6 - 2 - 0 - 4 -1.

As the "state" of the data is preserved each time we call dePoSit() or withDraw(), hence we get $350 after all.

Noted that that is a kind of "factory" function with "preload" data. You might think about another object when pass to myAccount(somedata); some other data. That is a really helpful way to create multiple objects from a factory function.

We get 21. First "youtube.com/hoccoban" returns 20 as we are using the property length of the string. Then it is being added one more value in ++this.x. The question here seems trivial but it is actually not. There is a crucial note we should keep in mind is that console.log(++this.x) will not work as x is undefined when it is called outside of the object.

We can solve the problem with this in this case by using arrow function in the inner so that is can become something like const inner = () => {} as the arrow function does not actually have this. It will automatically look around and call the available object when the function is executed.

The second solution is that we can somehow "bypass" the tricky this by using that/this solution. We just need to declare a new variable const that = this inside getMe() and before declaring inner function. That is a quite common practice.

The third solution is to take advantage of call(), bind() and apply() which are native methods of function (yes, function is also an object in JavaScript). In this case, we implement bind(this) to "bind" the function and the object so that this can actually point to the object when the function is executed. Note that bind() cannot be instantlly executed so that we need to add () after we bridge the function and the object. If we replace bind() with call(), then we do not need to pass () as in the above example. So inner.bind(this)(); will become inner.call(this);. They are technically equal. In practice, we tend to create a new variable to get the result from the binding of the function and the object.

First, take a closer look at the function. It has a asterisk (*) next to the keyword "function". We do not have return keyword inside the function itself. What is going on here?

It you have already known about generator, then this code snippet is not a big deal at all. We do not use generator very often, but this native JavaScript feature is the basis for async/await function, which is supported in ES7 that allows us to handle the flow of asynchronous code much easily.

The operator typeof data will return object rather than function, which is the same case with typeof hocCoBan(). Of course, typeof hocCoBan still returns function. But it is actually a normal function. Basically, we get 6 in the operator (typeof data).length.

Then data.next() calls the the built-in method next() which will output the value in the first yield, which is declared in the function. Then we get the length 9 with the string js.edu.vn.

After all, we get 15. Not that understanding generator is quite important if you really want to understand async/await function.

When using ... in array, it is called spread operator in JavaScript which, technically, is similar to rest parameter (using in the context of function). It provides a more elegant way to concat (combine) or copy array. In the code above, b is a copy of a. However, as we pass a in to a Set, it will return the unique value only in a. It means, now we have `[1, 2, "chó", 3, "mèo"] in b.

However, we then set the length for b as 3. Note that "chó".length returns 3 but in PHP, strlen("chó") returns 4, just in case you are coming from PHP world.

As we set the length for the array b, we also cut down the array itselt. That is the reason why we get [1, 2, "chó"] printing out in the console.

First, it should be noted that arguments cannot be used in an arrow function, so in order to take advantage of this feature, we have to write the function in the casual form. arguments returns an array-like object that contains any parameter we pass into the function when executing it.

... is a rest operator. We use this feature in function and array. Noted that in the context of array, it is called spread operator and it behaves differently. When declaring a function with ..., we can pass as many parameters into the function itselt when executing it as we want.

Note that in the function hai, we return arguments[arguments[0]] which means hai(1, 2, 3) will return 2 rathern than 1 because arguments[0] return 1 and then arguments[1] returns 2.

The last thing we have to take note is that the typeof operator of an array will return object, here the trick seems more daunting. The final anwser is 2 as we got it in a[1], or hai(1, 2, 3).

We have two simple classes in which Coder extends Component. Nothing fancy. As typeof ClassName returns function rather than class, we then get 8 in the operator "function".length.

Though we implement super(age) in the Coder class, we actually overwrite the contructor of the parent class Component in the child class Coder. Therefore, when initiating the object a, the following code is automatically triggered this.age = age -${typeof Coder}.length;. The difference between the child and parent 's constructor is minus (-) and plus (+) in the above code.

As such, we have 16 - 8 rather than 16 + 8, which returns 8. The function getAge() returns 9, so the corrent answer is C.

Bear in mind that JavaSCript is not a "real" OOP programming language even though we can now implement class and object as in other languages.

The key message that can be taken away in the code snippet above is filer(Boolean) which can be taken into consideration in case you want to eliminate falsy values in an array. We can use filter(callback) or filter(Boolean) in particular in this case to do that. Note that we have to pass into the filter function a callback and in this case Boolean is actually a function. You can check typeof Boolean to see it.

Similar to map or reduce function, filter always returns a new array from the exisiting one. [true, false, 1, 0, NaN, undefined, "", null, "js.edu.vn"].filter(Boolean); will return [true, 1, "js.edu.vn"];, hence calling the function removeFalse() gives us 3. So the correct answer is 3.

We have a simple array in the code snippet above that includes some digits, two other arrays and one object. Using the built-in function Number, we can convert any value passing to the function into digit. As coderfarm instanceof Array returns true, then converted get 1. Noted that you can use another way to check the type of an array is Array.isArrray(arrayToBeChecked) which return a boolean value. Suprisingly, the operator typeof [] returns object rather than array.

The built-in function indexOf will return the index of the element that is being checked. So as converted + true return 2, we are going to check the index of the element with the value 2 in the array coderfarm.

We get 4 in the console.log and the correct answer is D.

The operator ... in JavaScript is very handy. The function converter is quite trivial, it takes advantege of ... (rest operator || spread operator) to turn an array into an object.

First we have the constant checking with the value function given that Number(false) gives us 0 and that is the first index in the array content.

Second, the constant result gives us the value true as the typeof converter(content) is function, which is also the value of content[1].

Then in the final code, we have checking = true, and then result = true as well, so the final result is (typeof converter).length which is equivalent to "function".length because the typeof of converter is simply function. We get 8 after all and the correct answer is D.

So the key message here is that we can take advantate of the spread operator (or ...) to turn an array to an object. For example: const a = ["hello", 2], then we can have a go with const b = {...a} and b is now an object with the following value: {0: "hello", 1: 2}. The key of the object is actually the index of the original array.

We have a generator function in the code snippet above, which is defined with the *. Noted that we can "store" as many result as we want in a generator thanks to the keyword yield.

As the typeof js is function, so the length of the string function is 8. So when calling getJS.next().value;, we get 8. However, in the next calling, it returns 7, and in the following calling after that, we get 6. That is why generator can "store" and "release" (or return) as many value as we want.

So the answer is C, which is 8 (first execution of the generator) + 7 (second execution of the generator).

Array.prototype.some() is a built-in function facilitating us to iterate the array using a callback. As in the code snippet above, there are three parameters in the callback, namely currentValue (the value of the current element that is being checked), index (the index of the element in the array that is being checked/evaluated) and ages (the array itself).

The function some() returns a boolean value. The code currentValue > ages[ages.length - index] returns true only one time, which is the last element. Let 's examine the code when it runs through each element:

1. 10 > ages[4 - 0]. As ages[4] returns undefined, and 10 > undefined returns false, it stops.

2. 15 > ages[4 - 1]. As ages[3] returns 25, it breaks as the operator returns false.

3. 20 > ages[4 - 2]. As ages[2] returns 20, it breaks as the operator returns false.

4. 25 > ages[4 - 3]. As ages[1] returns 10, it returns true. Only this value is being pushed to the array response.

So response.push(currentValue + ages.length) will add the value 25 + 4 to the array response, D is the correct answer.

getString() is an arrow function with two parameters. As you can see that the parameter method has the default value false, then if you do not pass any value to it when executing the function, the default value will be used.

The key thing to take note from the code above is the difference betweet slice(1, 4) (which returns 3 characters) and substr(1, 4) (which returns 4 ones).

Finally console.log(getSTring("hello", true) + getSTring("hello")) returns 7 because slice and substr are both used.

The code above is a self-executing function. It runs when it is being declared. We have three parameters and three arguments passed are "hello", "world" and "new zealand".

First, arguments returns an object consisting of arguments passed to the function when executing it. However, using spread operator ..., we then convert the object to an array. We can also do it by using Array.from(object).

Second, slice(2, 3) extracts the element from the index 2 to the index 3, which returns "new zealand". It is still an array. We then extract the element with the index [0] and we get the string "new zealand" rather than an array.

Third, "new zealand".slice(3, 4) gives us an empty string (with a space between) " ". The Boolean(" ") gives us true. Noted that if there is no space in the empty string, we get false instead.

So the correct answer is B.

The code above is nothing much special. However it is written in a complicated way on purpose. First, we have a class named "HocCoBan" with two methods and one property. Then we add another method split using the tradional way (via prototype). Note that class in JavaScript is simply a syntactic sugar of function given that typeof ClassName return function.

When we call the method split, we pass the an empty string to it. This method then call other methods. The flow is as follows:

split("") ==> this.getSlice("") ==> this.getName("") ==> this.name.split(""). Here split is a built-in function that convert a string to an array.

Noted that in getSlice(), we also use .slice(true, this.name.length) to slice (cut) the array from the index 1 to 11. So the length is 10.

So the final answer is C.

This code might help us master the concept function prototype in JavaScript and the understand the difference between the built in function String.prototype.split and the function we declare by ourself HocCoBan.prototype.split.

Apart from learning some built-in functions to handle string such as replace and inclues, we are reviving the concept of currying function in JavaScript. Say you want to declare a function with three parameters, you may consider refactoring the code by declaring 3 nested functions, each with one parameter you wish to pass to. Basically, both of them work in the same way. However, noted that only the outerest (the main) function has the name as javaScript in the code above. Both nested (inner) functions are declared without the name. We also use three return keywords in the code.

When executing the function, you then have three () as in the javaScript("I love you")()(). We do not pass any argument into the second and third functions (both are inner/nested functions without the name) and these functions will take the default value we have alreaded declared when being executing.

All in all, we have the final operator return (node + deno + done).length; in which node is "I love you", deno is "love" and done is "I done you". The length of these strings is 24, which you can calculate by yourself the concatenated string I love youyou I done you. Be aware of the empty space, which is also taken into account.

The key information in the question above is about the method Array.prototype.find(). It returns the first element in the array that meets the condition declared in the callback function, which is passed to the function. The array is being iterated to check every single element. In the code above, we might easily see that the element world is the first element in the array that has a larger value than victory. Remember that "w" > "v" return trues if the two letters are compared. When two words are being compared, only the first letter in each word is being utilised to compare.

As the result, found is now world and thus found[1] returns the letter w whereas www[0][0] gives us the letter h in the element hello. It means found[1] < www[0][0] returns false.

So the final result is www[true ? 0: 1] or www[0], which is hello. And the correct answer is A.

We have a self-executing function with the parameter/argument is an empty array. Noted that NaN === NaN returns false, then age gets the value flag, which is an empty array. However, the boolean value is true when we call Boolean([]).

The function toString() returns the string true and the Number([]) returns 0. Then we get "t" in the console.log. The correct answer is B.

Keep in mind that Boolean([]) ==> true but Number([]) ==> 0. And sadly NaN === NaN returns false.

JavaScript is sometimes tedious to deal with given that it is a loosely type language. The data type of a variable can be changed depending on the value. An unexpected behaviour might unfortunately occur when you change/convert the original value to another one.

For example, the code 2 Number([]) returns 0 and 6 (Number({})) returns NaN, although both (Boolean([])) and (Boolean({})) return true.

In the code 9 Boolean(new Boolean(false)), we get true even though we pass into the function constructor Boolean() a false (as the) parameter. However, if we do not use the keyword new, then false will return. It seems that in Boolean(new Boolean(false)), we have a valid opreration, so it is true. However, in the Boolean(Boolean(false))) where we do not use the keyword new, we then get false because now a false value is being evaluated rather than an operation.

So, the correct answer is D.

Credit: @tiepphan, Vietnamese Angular Facebook group.

To answer the tricky question above, you might want to have a look at the concept of this in JavaScript (on browser environment). By default, this refers to window object. Note that Window (written in capital) is the Function constructor of the window object. In this regard, console.log(this === window) return true but console.log(this === Window) returns false.

As content() is an arrow function, this declared inside this function points to window, so myYoutube.content() returns myYoutube.getInfo(). Noted that we have to explicitly write myYoutube.getInfo() to make sure the code will run correctly as this in this case does not work as it does not refer to the currect object. In the function getInfo(), however, this actually refers to the currect object instead of window object because we use a normal function here.

Then we have the property name with the value "hoccoban". So the correct answer is A.

Credit: Thanks https://github.com/phanvigiaii for fixing the typo. Please make a pull request when you have time bro. Cheer.

We have a simple array that consists of 3 elements. If checking the type of the array with the operator typeof, we will have object. (Hint, you can make use of Array.isArray(array)) or array instanceof Array to check its type).

When declaring myArray.someProperty, we now add a new property to that array and when declaring Array.prototype.someOtherProperty = "hello", we add a new property to every single array.

As a result, the for... in loop will iterate through the array in question and return its key/property and the inherited property as well. However, in the second iteration, we take advantage of the method hasOwnProperty(key) to check whether a particular key/property actually belongs to the array in question rather than the inherited one.

In short, in the first iteration, we get 5 (3 original ones, 1 property that is directly added to the array, 1 inherited from the Array.prototype. In the second one, we only get 4 as the inherited property is not taken into consideration.

Keep in mind that, we use for... of to loop through an array or the traditional for loop. It is not a good practice to use for ... in to loop through an array. It is often used to loop through an object.

We are using destructure array (or object) technique to extract element of an array (or object). We also take advantage of ... (spread parameter) here.

The array we are destructuring is returned from a self-executing function. First we pass the parameter coderfarm, which is the parameter a when declaring the function. Then we update this array with some additional value (an array with three undefined elements using new Array(3)) on the top of the array (using unshift). The array is updated now as [[undefined, undefined, undefined], 1, 2, 3, 4, 5].

So top is the first element of the array or [undefined, undefined, undefined], which returns 3 when we check the length.

The bottom returns the rest of the array in question, which is 5 when using length property.

The final number is 8 and thus the correct answer is A.

The operator delete only works on the property of an object, not the object itself. In the code snippet above, we have a simple function getAge with the parameter flag. When the flag is true, we trigger delete age.number and if it is false, we will use the operator delete upon the whole object.

As this operator does not work on an object, if we can say that, it turns out that delete age actually does nothing. As such, console.log(getAge(false)) returns 10 and simultanously increases the value of age.number to 11. The value is now being kept in the memory. As such, console.log(age.number) will return 11.

When we pass the argument flag as true in the console.log(getAge(true)), we will trigger delete age.number which removes the value and the property age.number itself. It means age.number is now undefined. However, because we also attempt to increase the value of this undefined property using ++ operator, it returns NaN.

console.log(age.number) also returns NaN as well. So the correct answer is D.

We have three outputs in the code snippet above.

First console.log(cloneA.name); will return undefined but why? We use Object.assign to clone a new object from an empty and from the object copy. The object copy itself is actually created from the original object youtube using Object.create. Noted that because we use Object.create, copy will inherit the data from the original one but it is still an empty object itself.

Second, both console.log(cloneB.name) and console.log(copy.name) return "hoccoban" because cloneB.name will have the actual property name. On the contrary, copy.name outputs the property name inherited from the youtube.

So the correct answer is A.

We have a self-invoking function here and we pass an array to it when the function is executed. Note that Array.isArray(x) return true but actually we use ! before Array.isArray(x). It means data will return x.entries().

The method array.entries(), as you might have already known, returns a gererator. Here we will call next() to iterate through each element. Note that if you only call next() once, it will only return the first element instead of the whole iterator.

Then when we call value, it returns an array with the index and the value of the iterator. So what will we get if we call console.log(data.next().value[0]). Sure, it returns 0 as 0 is the index.

So the correct answer is B.

As x and y are both instances of symbol, they are unique in our codebase; therefore, the === comparison will return false as expected. In the simple code snippet above, we get the else operation.

It should be noted that the typeof x operation gives us symbol, and since a string in JavaScript is iterable, we get m as we pass in the index 2.

So the correct answer is D.

As frameworks is an array, it has a built-in method named Symbol.iterator. You can hence iterate through the whole array using commonly used methods such as for... of, normal for loop, forEach or map, among others. That is relatively trivial, I suppose.

This code challenge above is written to help us understand the concept of iteration better. First, we use the built-in method called entries() to create a new iteration. So does Symbol.iterator. Both seem to do the same thing.

Each time we call next() method, the iteration will output one element. We then can call value() to get the value. The difference between iterator and i is that the former shows the value itself while the latter outputs an array consisting of the index and the value. It means that in the code above, iterator.next().value returns angular and i.next().value gives us [1, angular].

So the correct answer is D.

We have two classes in the code snippet above. It sounds we are imitating React. The React class has only one property named theName, and no method is declared here. Providing that Author extends the React class, it inherits that property, surely. However, we have also declared another property with the same name in the Author classs. The difference is that the property declared in the child class is given the keyword static.

The Author class also has two methods with the same name render(), one as regular methods and another with static keyword. Will that work in JavaScript?

It turns out that JavaScript is quite flexible. It supports both property and method if they are declared with the same name as long as they are either regular property (or method) or static property (or method).

The last thing you should be aware of is that the method static render() only calls the static property, here is static theName = "Real React"; So does the regular method render(). As such, the code does not run into any issues.

So the correct answer is A.

js is a standard class declared in the code snippet above that has only one property with the name say. Then we again declare another property with the same name say for it. You might think that the property say has been overwritten with a new value goodbye.

That is not the case as we will get hello when we run console.log(new js().say);. It is clear that the JavaScript engine prioritizes the property declared inside the class more than the property declared later using the prototype mechanism.

If the property has not been declared inside the class itself, we can then add a new one with the help of prototype as in thename. Without the doubt, the code console.log(new js().thename); gives us google as expected.

So the correct answer is B.

To answer the question raised on the above code snippet, you might want to revisit two concepts, currying function and destructing array or object.

First, currying function means we convert a function with multiple parameters into multiple functions with a SINGLE parameter. Then you can easily manipulate the flow of the data. Noted that currying function is relevant to higher-order function, you might want to have a look.

destructing array or object means we attempt to extract a complex array or object more conveniently. For example, [y, x, z] = [10, 20, 30, 40] will extract y, x and z with the value 10, 20 and 30 respectively.

The last thing is incremental operator here ++x returns 21 but x++ does not as it still returns 21.

So the correct answer is C.

Array.prototype.reduce() is a bit perplexed built-in method that allows you to manipulate data in an array. It returns a single value from the array predefined as in the case with map or filter. The syntaxt of the function is arr.reduce(callback( accumulator, currentValue, [, index[, array]] )[, initialValue]), so it accepts a callback function with four arguments including accumulator, currentValue, currentIndex (optional) and array (optional).

The second argument of the reduce method, which is optional, is called initialValue that will be counted as the first element with the index 0 when reduce is executing. If initialValue is not provided, then reduce will run with the index 1 instead. reduce() sounds complicated, but truly it is not. In case you want to revise the function, kindly take a look at MDN here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/Reduce

The above code has two callback functions named callback and thecallback, which do the same thing. The seemingly creepy code is the variable sum, which is returned by a couple of nested reduce functions. It turns out that there is only one "real" reduce function and the other ones give us initialValue only.

• The first initialValue is 7;
• The first nested reduce function gives us 7 (initialValue) + 5 + 6 + 7 = 25.
• The second nested reduce has 25 as the initialValue, which we get from the above. Then it returns 25 + 5 + 6 + 7 = 43;
• The "real" reduce function now has 43 as the initialValue, the we get the final result: 43 + 5+ 6 + 7 = 61.

So the correct answer is D.

The code snippet above is relatively trivial. What we can learn from it is all about the spread operator (three-dot ...). Sometimes it is also used as a rest operator to extract data from an object or array.

We have two simple objects which both have the same key name but different values. The constant first gives us the length of the string value of the keyword name that is copied from a. So, first is now 12.

The constant second merges a and b into one object. However, as b has the same key name with a, the object created by merging two objects will have the value of b. It means the constant second gives us the length of youtube.com/hoccoban, which is 20.

third does the same thing with first and second as it merges two objects into one. However, it also adds another key-value to the object. Coincidently, the key now is name, which is the same with the key attained from a and b. Hence, this key and value will take over the merged object. That means third is the length of the string hello, which is 5.

In total, we have 12 + 20 + 5, and the final result is 37.

So the correct answer is B.

The code snippet above seems complicated regarding how we take advantage of Object.defineProperty to add key and value to the object hocCoBan. In fact, Object.defineProperty has a couple of handy features that allow us to control the behavior of the object in some situations where we want to make sure that the object created is mutable or not, whether it is iterable (using for..in) and so for. For example, if we set configurable: false when we declare an object with Object.defineProperty, we cannot use delete operator to delete the object's property. We cannot change the value of that property as well.

The second "take away" message when reading the code above is the unpacking object technique, or a more frequent term is the destructing object. Say you have an object with two keys called year and age, then you can get them by using the destructing object technique as follows: {year, age} = theOBject;. In the code above, when declaring the function App, we also use destructing object technique to get the key from the object and use them as the parameters.

If you are familiar with asynchronous code in JavaScript when using the keyword async, it is not a big deal to understand why we need to use then to get the function App being called. It fact, async always returns a promise, so we need to use then method to get the data we want.

The flow of the code is: 2021 - 30 + "hoccoban.com".length (which is 12).

The final result is 2003. So the correct answer is D.