Skip to content

Latest commit

 

History

History
77 lines (51 loc) · 7.05 KB

README-en.md

File metadata and controls

77 lines (51 loc) · 7.05 KB

How to go through the hungry Node.js interview?

Hi, welcome to ElemeFE, as shown in the title The purpose of this tutorial is to teach you how to get through the big front end of the interview, the position is 2 to 3 years experience Node.js server programmer, if you are on this job Interesting or learning Node.js some advanced content, then welcome to read.

It should be noted that this article is not for zero-based students, you need to have a certain JavaScript / Node.js basis, and have some work experience. In addition, the focus of this tutorial is more accurate to say that the server-based base Node. Js programmers need to understand the part.

If you think most do not understand, do not have to vote resume (so both sides save time) </ del>, if you think most have to understand or *** light to see the outline are very simple then welcome delivery resume To ElemeFe ([email protected]) ***.

guide

Although the purpose is to pass the interview, but this tutorial is not simply to list all the questions listed, and is the main interview will need to confirm whether you understand the point list out </ font> And to a certain degree of discussion.

This article classifies some of the common questions, each of which covers some coverage points' and lists a few 'common problems', usually these questions are 2 to 3 years of work experience that needs to be understood or confronted. Interested in a class of questions, or would like to know the answer to the question, you can read more content by reading more 'below.

Overall outline is not very comprehensive, the details of the coverage is not high, a lot of discussion is just the point to the end, I hope you take the problem to think.

coverage point

common problem

[Read more] (https://github.com/ElemeFE/node-interview/blob/master/sections/js-basic.md)

And front-end Js different, the back-end is the face of the server, more biased in terms of memory, for some more basic issues will be more concerned about.

common problem

  • A.js and b.js two files each other whether it will die cycle? Both sides can export variables? How to avoid this problem from the design? [[More]] (https://github.com/ElemeFE/node -interview / blob / master / sections / module.md # q-loop)
  • If a.js require b.js, then in the b definition of the global variable t = 111 can be printed directly in a? [[More]] (https://github.com/ElemeFE/node- Interview / blob / master / sections / module.md # q-global)
  • How do I update a js / json file without restarting the node process? Is there a problem with the problem? [[More]] (https://github.com/ElemeFE/node-interview/blob/master/sections /module.md#q-hot)

[Read more] (https://github.com/ElemeFE/node-interview/blob/master/sections/module.md)

common problem

[Read more] (https://github.com/ElemeFE/node-interview/blob/master/sections/event-async.md)