Exam

Question 1

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

The var statement

Question 1

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Hoisting

Answer 1

When the execution phase begins, JavaScript knows what variables exist and where they are in scope. From the developer’s perspective, the code acts like the declarations were moved to the top of their respective scope. In particular, function-scoped declarations are moved to the function’s beginning, and block-scoped declarations are moved to the block’s start. We call this process hoisting.

The effect of hoisting is that all the declarations get hoisted – raised, lifted, moved – to the top of their defined scope. That’s why the following code works:

Question 2

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Strict mode

Question 3

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Closures, scope, and private data

Question 4

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Partial function application

Question 5

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

IIFEs

Question 6

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Shorthand notation (understanding, not using)

Question 7

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Modules (CommonJS)

Question 8

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Exceptions

Question 9

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Pure functions and side effects

Question 10

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Asynchronous programming (setTimeout, setInterval)

Question 11

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Testing terminology

Question 12

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Jest

Question 13

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

expect and matchers (toBe and toEqual especially)

Question 14

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

SEAT approach

Question 15

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Understanding code coverage

Question 16

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Writing tests

Question 17

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

Project directory layout

Question 18

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

what is transpilation

Question 19

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

npm and npx

Question 20

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

package.json and package-lock.json

Question 21

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

npm scripts

Question 22

Explain to someone who doesn’t know about (but knows everything up to knowing about it) with at least 1 example:

packaging projects