Comment by Dong Nguyen on "Where does frontend JavaScript end, and Node.js begin?"

Node.js is a part of front-end nowadays. There is no frontier between them. You should look Node.js as a tool.

If you mean the distinction between backend and frontend development. I would like to remind you of Universal JavaScript (aka Isomorphism JavaScript). With its appearance, the boundary between server side and client side has almost been removed.

On another point of view, JavaScript includes at least 3 areas:

ECMAScript: the core of language
Web APIs: anything JavaScript can do at client side
Node.js APIs: relating to JavaScript's ability at server side

So if you really need a clear boundary, you might consider to look at there areas.

I am sorry, how can nodeJS be part of front end? It is being used as a front end code server at best, but it is still a server side runtime environment. That thing you just said could confuse many. Being a full stack developer, I know the difference here, but not everyone shares my clarity. So I guess you should make things more clear.

By saying "Node.js is a part of front-end", I mean that we can use Node.js to:

setup front-end environment and tool
transpile ES.Next, compile CSS.Next, etc
build website, generate static site
run test, especially E2E test

And more.

Though I agree with the 3 areas of Javascript, I still think this answer is more confusing than anything.

The tasks you describe could be done by PHP or any other "framework / plateform" running on the server.

What you said is not wrong per say, but confusing. All the tasks you listed will never run in the browser. Their result can be executed in the browser, that is different.

Search Hashnode