I started to translate this into Japanese. https://github.com/KenjiI/javascript-tutorial-ja

This issue is for informing about that. If some rules when I translate this, please let me know!

Hello, Ilya and the Team!

The modern JavaScript tutorial in Korean is almost ready to publish(Part 1 is translated, almost), finally! 👍 👍 👍 https://github.com/javascript-tutorial/en.javascript.info/issues/1149

Please let me know what I need to do to publish the Korean ver.

Hi, It seems like we've made it at fa.javascript.info! 🥳

As mentioned in the "Publish" part of this page, it's now more than half-finished.

cc @iliakan

People sometimes like to read in low light environments, adding a dark mode button is a good idea for that. The changes will only be made in css and, of course, add a new button for that. If this approved I can work on this.

As a modern tutorial on modern JS, please consider replacing all instances of the legacy alert() function with console.log. Especially for a work with the aim to teach proper JS and modern patterns, showing (let alone teaching) alert hampers learners by teaching them a function that no one should be using anymore. Looking at the dev console is an integral part of learning modern JS, and the Console API has been a much better friend to learners and seasons devs alike since 2010 than alert ever was.

The word "Chapter" seems to be used for 3 different levels in the tutorial. On the sidebar for "The Javascript Language" section: https://javascript.info/js

other such high-level sections, such as: Browser: Document, Events, Interfaces Frames and windows Binary data, files Network requests Storing data in the browser Animation Web components Regular expressions

are referred to as "Sibling Chapters". However, if you go deeper into the "JavaScript Language" "chapter", you will then find lower-level divisions also referred to as "chapters": Sibling chapters An introduction JavaScript Fundamentals Code quality Objects: the basics Data types Advanced working with functions Object properties configuration Prototypes, inheritance Classes Error handling Promises, async/await Generators, advanced iteration Modules Miscellaneous

Then, in one of those sections if you go to one of the options, like "Hello, World!" under JavaScript Fundamentals", you find that sections like "Hello, World!" and the like are referred to in the sidebar as "lessons" (which I think is totally appropriate). However, within the lessons, when prior lessons are referred to, they are generally called "chapters". E.g. in the lesson "Object to primitive conversion", we find:

"In the chapter Type Conversions we’ve seen the rules for numeric, string and boolean conversions of primitives. But we left a gap for objects. Now, as we know about methods and symbols it becomes possible to fill it."

But, using the terminology from the sidebar, "Type Conversions" is a "lesson", not a "chapter". In another lesson (sorry, don't recall which one right now) where an earlier lesson (lesson "Data types" within the chapter "JavaScript fundamentals" https://javascript.info/types) was called a "chapter" it was especially ambiguous because there actually was a chapter ("Data types" https://javascript.info/data-types) with the same name.

There is an "Army of functions" exercise in this chapter. And I suggest some modifications for the explanation/solution.

If I understand correctly, using let doesn't create a new Lexical Environment and it is the {} block clause creates a new Lexical Environment each time and let just creates a local variable inside the Lexical Environment, while var hoists the variable into the function level scope when creating a variable. So, whether using let or not, there is a new Lexical Environment created each run in for(){} or while{}.

But for the first time I read the solution/explanation, I thought it was using let that creates a new Lexical Environment. Kinda misleading until I read some thing on MDN about let.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/let

However, it's important to point out that a block nested inside a case clause will create a new block scoped lexical environment, which will not produce the redeclaration errors shown above.

The quotes above did not direclty clear my doubt but made me thought twice. And then I got my coherent conclusion.

Parts that made me mostly confused for the first time:

Now it works correctly, because every time the code block in for (let i=0...) {...} is executed, a new Lexical Environment is created for it, with the corresponding variable i.

The while loop, just like for, makes a new Lexical Environment for each run. So here we make sure that it gets the right value for a shooter.

And becasue you are adding a new let or replacing var with let in each new code snippet. So I was more likey to believe that it was let that somehow creates a new Lexical Environment.

To sum up, I suggest making some modification here and let the readers know let does not create a new Lexical Environment, while {} does.

Anyway, it's just my opinion. (Or my conclusion could totally be wrong. I write C++ most of my times.)

--

In the end, I would like to thank you so much for the tutorial. It's so far the best I could find in the Net. So much better than the classic book I've read. I am going to buy a full tutorial.

Hello @iliakan! Time ago I contact you to start this project. Finally, I can get through this with some other people. This is the repository https://github.com/lizzie136/javacript-tutorial-es

Can you include it in the list, I'll be updating it as soon as possible.

Thanks!!

Elizabeth

There may probably be one out there, but I think a Discord Server or Telegram Group would be a really nice addition to the course, not only would we be able to communicate with classmates and discuss solutions to the course, but then we would also be able to find study groups, I think it'll be a really useful addition.

PS: I don't know if there's one, I never saw any mention of any, but if there is, I'll be more than willing to join in.

WIP ? What's wrong with it? Something new?

I just reviewed the translated article!!!! give us a break

ok, just to report a redundancy, keep in mind in the new version.

No changes intended by my own line 53 Dont know English. I should avoid the coma in Spanish. You mean: To avoid confusion: (example) or To avoid (ambiguity? should truncate? should leave bigint?) confusion, it's not supported on bigints:

A few tweaks and improvements: line 3: more verbose language line 50: shorthand is a better description, also added in the same line for clarity line 89: grammar fix line 91: grammar fix line 144: added whereas for clarity line 161: minor tweak line 165: replaced that with this because it could make more sense lines 171,195,233: minor tweaks line 202: grammar fix line 225: replaced huge ones with huge values to be more specific line 251: minor tweak line 253: formatting: added spaces line 304: improvement suggestion: switch action at the beginning line 324: used the same language as in line 312 for consistency. line 347: considered that the two sentences belong together, making the idea be clearer line 441: improved flow line 444: formatting: removed space task 2: formatting: added spaces task 3: description suggestion

Current: Modern build tools, such as webpack and others, bundle modules together and optimize them to speedup loading. They also removed unused imports. Expected: Modern build tools, such as webpack and others, bundle modules together and optimize them to speedup loading. They also remove unused imports.

Current: For instance, if you import * as library from a huge code library, and then use only few methods, then unused ones will not be included into the optimzed bundle. Expected: For instance, if you import * as library from a huge code library, and then use only few methods, then unused ones will not be included into the optimized bundle.

Hello!

Not sure if requests fit here, but would it possible to expand the explanations to explain what CSRF cookies are and how they work? There is an explanation on CORS so I would propose to have it next to one another.

In the Non-writable and Non-configurable section, the comments in a few of the code snippets says 'Error' but that is only the case when the 'strict' mode is enabled. I understand that it is also mentioned but it should be reflected in the code snippet as well so that the reader is absolutely clear about the concept.