Timeline for How is the 'use strict' statement interpreted in Node.js?
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2020 at 18:48 | comment | added | ahmed hamdy | I think Node.js not include full Ecmascript 6 Module (which support Strict Mode by default), see this useful article here (discuss usage of Strict mode into Javascript/Node.js) => tvernon.tech/blog/javascript-strict-mode | |
| Jun 29, 2017 at 14:35 | comment | added | Amol M Kulkarni | @fider: Though your question is not very clear to me. You can consider asking a new question or continue explaining in comment if its relevant to this question asked. Before that have a look at this link if you can find the answer | |
| Jun 23, 2017 at 12:54 | comment | added | fider |
@AmolMKulkarni : "Module code is always strict mode code" - it is not exactly true for Node. If you will not use 'use strict' in node v.6.10.2 following code will not throw error: var obj = {}; Object.preventExtensions(obj); obj.a=1;
|
|
| May 23, 2017 at 12:34 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Dec 17, 2016 at 11:53 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Copy edited.
|
| May 13, 2016 at 13:57 | history | edited | Amol M Kulkarni | CC BY-SA 3.0 |
Updated the latest relevant information
|
| Dec 11, 2015 at 19:42 | history | edited | Anti Veeranna | CC BY-SA 3.0 |
fixed out of date link to strict mode compatibility table
|
| Jul 14, 2015 at 6:08 | history | edited | Unihedron | CC BY-SA 3.0 |
added 1 character in body
|
| Aug 24, 2013 at 12:15 | vote | accept | Community Bot | ||
| Aug 24, 2013 at 11:29 | history | edited | Amol M Kulkarni | CC BY-SA 3.0 |
added 234 characters in body
|
| Aug 24, 2013 at 11:21 | history | edited | Amol M Kulkarni | CC BY-SA 3.0 |
added 137 characters in body
|
| Aug 24, 2013 at 11:15 | history | edited | Amol M Kulkarni | CC BY-SA 3.0 |
added 137 characters in body
|
| Aug 24, 2013 at 11:00 | comment | added | Amol M Kulkarni | @GabrielLlamas: Thanks. @ Golo Roden: Yes, if commented properly. we can give more better answers. | |
| Aug 24, 2013 at 10:52 | history | edited | Amol M Kulkarni | CC BY-SA 3.0 |
added 193 characters in body
|
| Aug 24, 2013 at 10:50 | comment | added | Golo Roden | First of all, Chrome is not the only browser on the planet. Just that Node.js and Chrome use V8, does not mean neccessarily that it works the same in all browsers. Second, there is a difference in the way, files (aka modules) are loaded. Third, scripts for browsers get usually concatenated for production use, and that's where problems may arise when you just say that both are the same environments. They're not. V8 is not the only important thing when it comes to executing Node.js files. | |
| Aug 24, 2013 at 10:47 | history | edited | Amol M Kulkarni | CC BY-SA 3.0 |
added 193 characters in body
|
| Aug 24, 2013 at 10:36 | history | edited | Amol M Kulkarni | CC BY-SA 3.0 |
added 308 characters in body
|
| Aug 24, 2013 at 10:30 | history | answered | Amol M Kulkarni | CC BY-SA 3.0 |