Improved JavaScript Roadmap (#6779)
* - Fixed Spacing and EOL. - Fixed Wrong Spellings. - Improved Examples. * ## Adding Content for : - Add `apply()` - Add `bind()` - Add `call()`pull/6823/head^2
parent
90486c2369
commit
5c2cc7a6da
28 changed files with 79 additions and 50 deletions
@ -1 +1,7 @@ |
||||
# bind |
||||
# bind() |
||||
|
||||
`bind()` method creates a new function with a fixed this value. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Bind Method - MDN Docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/bind) |
||||
|
@ -1,8 +1,8 @@ |
||||
# TypeOf Operator |
||||
# `typeof` Operator |
||||
|
||||
You can use the typeOf operator to find the data type of a JavaScript variable. It returns a string indicating the type of provided operand's value. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Typeof Reference](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/typeof) |
||||
- [@article@Typeof Live Examples](https://www.w3schools.com/js/tryit.asp?filename=tryjs_typeof_all) |
||||
- [@article@typeof Reference](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/typeof) |
||||
- [@article@typeof Live Examples](https://www.w3schools.com/js/tryit.asp?filename=tryjs_typeof_all) |
||||
|
@ -1,12 +1,13 @@ |
||||
# Javascript chrome dev tools |
||||
# JavaScript Chrome Dev Tools |
||||
|
||||
These are a set of tools built into the browser to aid frontend developers diagnose and solve various issues in their applications — such as JavaScript and logical bugs, CSS styling issues or even just making quick temporary alterations to the DOM. |
||||
|
||||
To enter the dev tools, right click and click **Inspect** (or press `ctrl+shift+c`/`cmd+opt+c`) to enter the Elements panel. Here you can debug CSS and HTML issues. If you want to see logged messages or interact with javascript, enter the **Console** tab from the tabs above (or press `ctrl+shift+j` or `F12` /`cmd+opt+j` to enter it directly). Another very useful feature in the Chrome dev tools is the Lighthouse (for checking performance). |
||||
To enter the dev tools, right click and click **Inspect** (or press `ctrl+shift+c`/`cmd+opt+c`) to enter the Elements panel. Here you can debug CSS and HTML issues. If you want to see logged messages or interact with javascript, enter the **Console** tab from the tabs above (or press `ctrl+shift+j` or `F12` / `cmd+opt+j` to enter it directly). Another very useful feature in the Chrome dev tools is the Lighthouse (for checking performance). |
||||
|
||||
NOTE: This isn't a chrome-specific feature, and most browsers (Chromium based or otherwise) will have their own, largely-similar set of devtools. |
||||
|
||||
Visit the following resources to learn more: |
||||
|
||||
- [@article@Official Docs](https://developer.chrome.com/docs/devtools/overview/) |
||||
- [@official@Official Docs](https://developer.chrome.com/docs/devtools/) |
||||
- [@official@Debug JavaScript with Chrome Dev Tools](https://developer.chrome.com/docs/devtools/javascript/) |
||||
- [@feed@Explore top posts about JavaScript](https://app.daily.dev/tags/javascript?ref=roadmapsh) |
||||
|
Loading…
Reference in new issue