mirror of
https://github.com/kamranahmedse/developer-roadmap.git
synced 2026-03-14 10:41:57 +08:00
Compare commits
48 Commits
fix/markdo
...
questions/
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
e6cbf55a38 | ||
|
|
d66d4bcb8a | ||
|
|
932896c3af | ||
|
|
1539c6ccaf | ||
|
|
84aa35cdec | ||
|
|
b6a852b29b | ||
|
|
2d2f670153 | ||
|
|
5cf7aa340f | ||
|
|
601d21ca9d | ||
|
|
a5527dd872 | ||
|
|
4d6d943b4e | ||
|
|
85214da400 | ||
|
|
46eb27a810 | ||
|
|
e47bd63cc9 | ||
|
|
d314f3d8c1 | ||
|
|
52fdd8f07d | ||
|
|
22f59c66f0 | ||
|
|
4a862241d3 | ||
|
|
b1fdc7ff49 | ||
|
|
445bdabde5 | ||
|
|
c46b4220a7 | ||
|
|
cdcdfc4973 | ||
|
|
d4b4b3c55c | ||
|
|
2c0ebe4209 | ||
|
|
c51438142c | ||
|
|
d5a47b79db | ||
|
|
ca2a75537e | ||
|
|
f62faf214c | ||
|
|
00b9630669 | ||
|
|
49ba524c15 | ||
|
|
d4436e8a8f | ||
|
|
e0b3209dc4 | ||
|
|
cf5dd19652 | ||
|
|
16680e2629 | ||
|
|
b9b12333cb | ||
|
|
8a9bb60211 | ||
|
|
2c6bef62b2 | ||
|
|
efb7e13f7d | ||
|
|
b34c7eff65 | ||
|
|
15c43fda5d | ||
|
|
b38f34a722 | ||
|
|
f1780fabda | ||
|
|
5362a64c29 | ||
|
|
720809f139 | ||
|
|
5b03601aa2 | ||
|
|
90df308751 | ||
|
|
3c0545e54f | ||
|
|
4eb145dff4 |
24
package.json
24
package.json
@@ -22,24 +22,24 @@
|
||||
"test:e2e": "playwright test"
|
||||
},
|
||||
"dependencies": {
|
||||
"@astrojs/react": "^3.0.7",
|
||||
"@astrojs/react": "^3.0.8",
|
||||
"@astrojs/sitemap": "^3.0.3",
|
||||
"@astrojs/tailwind": "^5.0.3",
|
||||
"@astrojs/tailwind": "^5.0.4",
|
||||
"@fingerprintjs/fingerprintjs": "^4.2.1",
|
||||
"@nanostores/react": "^0.7.1",
|
||||
"@types/react": "^18.2.43",
|
||||
"@types/react-dom": "^18.2.17",
|
||||
"astro": "^4.0.3",
|
||||
"@types/react": "^18.2.45",
|
||||
"@types/react-dom": "^18.2.18",
|
||||
"astro": "^4.0.7",
|
||||
"astro-compress": "^2.2.3",
|
||||
"clsx": "^2.0.0",
|
||||
"dracula-prism": "^2.1.13",
|
||||
"jose": "^5.1.3",
|
||||
"js-cookie": "^3.0.5",
|
||||
"lucide-react": "^0.294.0",
|
||||
"lucide-react": "^0.300.0",
|
||||
"nanoid": "^5.0.4",
|
||||
"nanostores": "^0.9.5",
|
||||
"node-html-parser": "^6.1.11",
|
||||
"npm-check-updates": "^16.14.11",
|
||||
"npm-check-updates": "^16.14.12",
|
||||
"prismjs": "^1.29.0",
|
||||
"react": "^18.2.0",
|
||||
"react-confetti": "^6.1.0",
|
||||
@@ -48,8 +48,8 @@
|
||||
"rehype-external-links": "^3.0.0",
|
||||
"roadmap-renderer": "^1.0.6",
|
||||
"slugify": "^1.6.6",
|
||||
"tailwind-merge": "^2.1.0",
|
||||
"tailwindcss": "^3.3.6",
|
||||
"tailwind-merge": "^2.2.0",
|
||||
"tailwindcss": "^3.4.0",
|
||||
"zustand": "^4.4.7"
|
||||
},
|
||||
"devDependencies": {
|
||||
@@ -58,11 +58,11 @@
|
||||
"@types/js-cookie": "^3.0.6",
|
||||
"@types/prismjs": "^1.26.3",
|
||||
"csv-parser": "^3.0.0",
|
||||
"gh-pages": "^6.1.0",
|
||||
"gh-pages": "^6.1.1",
|
||||
"js-yaml": "^4.1.0",
|
||||
"markdown-it": "^14.0.0",
|
||||
"openai": "^4.20.1",
|
||||
"prettier": "^3.1.0",
|
||||
"openai": "^4.24.1",
|
||||
"prettier": "^3.1.1",
|
||||
"prettier-plugin-astro": "^0.12.2",
|
||||
"prettier-plugin-tailwindcss": "^0.5.9"
|
||||
}
|
||||
|
||||
280
pnpm-lock.yaml
generated
280
pnpm-lock.yaml
generated
@@ -6,14 +6,14 @@ settings:
|
||||
|
||||
dependencies:
|
||||
'@astrojs/react':
|
||||
specifier: ^3.0.7
|
||||
version: 3.0.7(@types/react-dom@18.2.17)(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)(vite@5.0.7)
|
||||
specifier: ^3.0.8
|
||||
version: 3.0.8(@types/react-dom@18.2.18)(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)(vite@5.0.10)
|
||||
'@astrojs/sitemap':
|
||||
specifier: ^3.0.3
|
||||
version: 3.0.3
|
||||
'@astrojs/tailwind':
|
||||
specifier: ^5.0.3
|
||||
version: 5.0.3(astro@4.0.3)(tailwindcss@3.3.6)
|
||||
specifier: ^5.0.4
|
||||
version: 5.0.4(astro@4.0.7)(tailwindcss@3.4.0)
|
||||
'@fingerprintjs/fingerprintjs':
|
||||
specifier: ^4.2.1
|
||||
version: 4.2.1
|
||||
@@ -21,14 +21,14 @@ dependencies:
|
||||
specifier: ^0.7.1
|
||||
version: 0.7.1(nanostores@0.9.5)(react@18.2.0)
|
||||
'@types/react':
|
||||
specifier: ^18.2.43
|
||||
version: 18.2.43
|
||||
specifier: ^18.2.45
|
||||
version: 18.2.45
|
||||
'@types/react-dom':
|
||||
specifier: ^18.2.17
|
||||
version: 18.2.17
|
||||
specifier: ^18.2.18
|
||||
version: 18.2.18
|
||||
astro:
|
||||
specifier: ^4.0.3
|
||||
version: 4.0.3(typescript@5.2.2)
|
||||
specifier: ^4.0.7
|
||||
version: 4.0.7(typescript@5.2.2)
|
||||
astro-compress:
|
||||
specifier: ^2.2.3
|
||||
version: 2.2.3
|
||||
@@ -45,8 +45,8 @@ dependencies:
|
||||
specifier: ^3.0.5
|
||||
version: 3.0.5
|
||||
lucide-react:
|
||||
specifier: ^0.294.0
|
||||
version: 0.294.0(react@18.2.0)
|
||||
specifier: ^0.300.0
|
||||
version: 0.300.0(react@18.2.0)
|
||||
nanoid:
|
||||
specifier: ^5.0.4
|
||||
version: 5.0.4
|
||||
@@ -57,8 +57,8 @@ dependencies:
|
||||
specifier: ^6.1.11
|
||||
version: 6.1.11
|
||||
npm-check-updates:
|
||||
specifier: ^16.14.11
|
||||
version: 16.14.11
|
||||
specifier: ^16.14.12
|
||||
version: 16.14.12
|
||||
prismjs:
|
||||
specifier: ^1.29.0
|
||||
version: 1.29.0
|
||||
@@ -73,7 +73,7 @@ dependencies:
|
||||
version: 18.2.0(react@18.2.0)
|
||||
reactflow:
|
||||
specifier: ^11.10.1
|
||||
version: 11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
version: 11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
rehype-external-links:
|
||||
specifier: ^3.0.0
|
||||
version: 3.0.0
|
||||
@@ -84,14 +84,14 @@ dependencies:
|
||||
specifier: ^1.6.6
|
||||
version: 1.6.6
|
||||
tailwind-merge:
|
||||
specifier: ^2.1.0
|
||||
version: 2.1.0
|
||||
specifier: ^2.2.0
|
||||
version: 2.2.0
|
||||
tailwindcss:
|
||||
specifier: ^3.3.6
|
||||
version: 3.3.6
|
||||
specifier: ^3.4.0
|
||||
version: 3.4.0
|
||||
zustand:
|
||||
specifier: ^4.4.7
|
||||
version: 4.4.7(@types/react@18.2.43)(react@18.2.0)
|
||||
version: 4.4.7(@types/react@18.2.45)(react@18.2.0)
|
||||
|
||||
devDependencies:
|
||||
'@playwright/test':
|
||||
@@ -99,7 +99,7 @@ devDependencies:
|
||||
version: 1.40.1
|
||||
'@tailwindcss/typography':
|
||||
specifier: ^0.5.10
|
||||
version: 0.5.10(tailwindcss@3.3.6)
|
||||
version: 0.5.10(tailwindcss@3.4.0)
|
||||
'@types/js-cookie':
|
||||
specifier: ^3.0.6
|
||||
version: 3.0.6
|
||||
@@ -110,8 +110,8 @@ devDependencies:
|
||||
specifier: ^3.0.0
|
||||
version: 3.0.0
|
||||
gh-pages:
|
||||
specifier: ^6.1.0
|
||||
version: 6.1.0
|
||||
specifier: ^6.1.1
|
||||
version: 6.1.1
|
||||
js-yaml:
|
||||
specifier: ^4.1.0
|
||||
version: 4.1.0
|
||||
@@ -119,17 +119,17 @@ devDependencies:
|
||||
specifier: ^14.0.0
|
||||
version: 14.0.0
|
||||
openai:
|
||||
specifier: ^4.20.1
|
||||
version: 4.20.1
|
||||
specifier: ^4.24.1
|
||||
version: 4.24.1
|
||||
prettier:
|
||||
specifier: ^3.1.0
|
||||
version: 3.1.0
|
||||
specifier: ^3.1.1
|
||||
version: 3.1.1
|
||||
prettier-plugin-astro:
|
||||
specifier: ^0.12.2
|
||||
version: 0.12.2
|
||||
prettier-plugin-tailwindcss:
|
||||
specifier: ^0.5.9
|
||||
version: 0.5.9(prettier-plugin-astro@0.12.2)(prettier@3.1.0)
|
||||
version: 0.5.9(prettier-plugin-astro@0.12.2)(prettier@3.1.1)
|
||||
|
||||
packages:
|
||||
|
||||
@@ -149,21 +149,18 @@ packages:
|
||||
resolution: {integrity: sha512-o/ObKgtMzl8SlpIdzaxFnt7SATKPxu4oIP/1NL+HDJRzxfJcAkOTAb/ZKMRyULbz4q+1t2/DAebs2Z1QairkZw==}
|
||||
dev: true
|
||||
|
||||
/@astrojs/compiler@2.3.2:
|
||||
resolution: {integrity: sha512-jkY7bCVxl27KeZsSxIZ+pqACe+g8VQUdTiSJRj/sXYdIaZlW3ZMq4qF2M17P/oDt3LBq0zLNwQr4Cb7fSpRGxQ==}
|
||||
/@astrojs/compiler@2.3.4:
|
||||
resolution: {integrity: sha512-33/YtWoBCE0cBUNy1kh78FCDXBoBANX87ShgATlAHECYbG2+buNTAgq4Xgz4t5NgnEHPN21GIBC2Mvvwisoutw==}
|
||||
dev: false
|
||||
|
||||
/@astrojs/internal-helpers@0.2.1:
|
||||
resolution: {integrity: sha512-06DD2ZnItMwUnH81LBLco3tWjcZ1lGU9rLCCBaeUCGYe9cI0wKyY2W3kDyoW1I6GmcWgt1fu+D1CTvz+FIKf8A==}
|
||||
dev: false
|
||||
|
||||
/@astrojs/markdown-remark@4.0.0(astro@4.0.3):
|
||||
resolution: {integrity: sha512-JSrn49fJGuH/0S2TTGxLK7bNDspOakJWZVFHeP+IDFjWdghT4HtsTShS2EiISNx3zfOFBAwy5Cj4xT4U5BWNeA==}
|
||||
peerDependencies:
|
||||
astro: ^4.0.0-beta.0
|
||||
/@astrojs/markdown-remark@4.0.1:
|
||||
resolution: {integrity: sha512-RU4ESnqvyLpj8WZs0n5elS6idaDdtIIm7mIpMaRNPCebpxMjfcfdwcmBwz83ktAj5d2eO5bC3z92TcGdli+lRw==}
|
||||
dependencies:
|
||||
'@astrojs/prism': 3.0.0
|
||||
astro: 4.0.3(typescript@5.2.2)
|
||||
github-slugger: 2.0.0
|
||||
import-meta-resolve: 4.0.0
|
||||
mdast-util-definitions: 6.0.0
|
||||
@@ -188,8 +185,8 @@ packages:
|
||||
prismjs: 1.29.0
|
||||
dev: false
|
||||
|
||||
/@astrojs/react@3.0.7(@types/react-dom@18.2.17)(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)(vite@5.0.7):
|
||||
resolution: {integrity: sha512-MpjuFw7YGta44OaQExKVCWyXjujUtUsp5Nst/wIjRHbkmBBlypdj+MF9/xqjsYM+vjcrByOGupmluRrFQO67YQ==}
|
||||
/@astrojs/react@3.0.8(@types/react-dom@18.2.18)(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)(vite@5.0.10):
|
||||
resolution: {integrity: sha512-EiIWgiRmw4rAxl2+AUK9VBdKvQrOgG/33dTeP+CX3iPzvlx51deaaHwlJIqEQCIIc6qgaIrXEhsJh8NyG9mxJQ==}
|
||||
engines: {node: '>=18.14.1'}
|
||||
peerDependencies:
|
||||
'@types/react': ^17.0.50 || ^18.0.21
|
||||
@@ -197,9 +194,9 @@ packages:
|
||||
react: ^17.0.2 || ^18.0.0
|
||||
react-dom: ^17.0.2 || ^18.0.0
|
||||
dependencies:
|
||||
'@types/react': 18.2.43
|
||||
'@types/react-dom': 18.2.17
|
||||
'@vitejs/plugin-react': 4.2.1(vite@5.0.7)
|
||||
'@types/react': 18.2.45
|
||||
'@types/react-dom': 18.2.18
|
||||
'@vitejs/plugin-react': 4.2.1(vite@5.0.10)
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
ultrahtml: 1.5.2
|
||||
@@ -215,17 +212,17 @@ packages:
|
||||
zod: 3.22.4
|
||||
dev: false
|
||||
|
||||
/@astrojs/tailwind@5.0.3(astro@4.0.3)(tailwindcss@3.3.6):
|
||||
resolution: {integrity: sha512-p+uFa1PNuV8RxhGkPUFgVq8CUbmS3xr0u5k1An2xKECLotRh7vsrGcPUijHvYOt42URohcg8rIq0CxNoVMhReg==}
|
||||
/@astrojs/tailwind@5.0.4(astro@4.0.7)(tailwindcss@3.4.0):
|
||||
resolution: {integrity: sha512-50ImfEFRBjndtWus6xJOWQ4EVpZWB4d+hieosMPm1Tca68mNTX+Yi1/PhTMk9q/w7iZPIUK/KGBoovo15O10eQ==}
|
||||
peerDependencies:
|
||||
astro: ^3.0.0 || ^4.0.0
|
||||
tailwindcss: ^3.0.24
|
||||
dependencies:
|
||||
astro: 4.0.3(typescript@5.2.2)
|
||||
autoprefixer: 10.4.16(postcss@8.4.31)
|
||||
postcss: 8.4.31
|
||||
postcss-load-config: 4.0.2(postcss@8.4.31)
|
||||
tailwindcss: 3.3.6
|
||||
astro: 4.0.7(typescript@5.2.2)
|
||||
autoprefixer: 10.4.16(postcss@8.4.32)
|
||||
postcss: 8.4.32
|
||||
postcss-load-config: 4.0.2(postcss@8.4.32)
|
||||
tailwindcss: 3.4.0
|
||||
transitivePeerDependencies:
|
||||
- ts-node
|
||||
dev: false
|
||||
@@ -1074,39 +1071,39 @@ packages:
|
||||
config-chain: 1.1.13
|
||||
dev: false
|
||||
|
||||
/@reactflow/background@11.3.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0):
|
||||
/@reactflow/background@11.3.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0):
|
||||
resolution: {integrity: sha512-06FPlSUOOMALEEs+2PqPAbpqmL7WDjrkbG2UsDr2d6mbcDDhHiV4tu9FYoz44SQvXo7ma9VRotlsaR4OiRcYsg==}
|
||||
peerDependencies:
|
||||
react: '>=17'
|
||||
react-dom: '>=17'
|
||||
dependencies:
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
classcat: 5.0.4
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.43)(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.45)(react@18.2.0)
|
||||
transitivePeerDependencies:
|
||||
- '@types/react'
|
||||
- immer
|
||||
dev: false
|
||||
|
||||
/@reactflow/controls@11.2.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0):
|
||||
/@reactflow/controls@11.2.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0):
|
||||
resolution: {integrity: sha512-4QHT92/ACVlZkvV+Hq44bAPV8WbMhkJl+/J0EbXcqQ1+an7cWJsF84eeelJw7R5J76RoaSSpKdsWsL2v7HAVlw==}
|
||||
peerDependencies:
|
||||
react: '>=17'
|
||||
react-dom: '>=17'
|
||||
dependencies:
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
classcat: 5.0.4
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.43)(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.45)(react@18.2.0)
|
||||
transitivePeerDependencies:
|
||||
- '@types/react'
|
||||
- immer
|
||||
dev: false
|
||||
|
||||
/@reactflow/core@11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0):
|
||||
/@reactflow/core@11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0):
|
||||
resolution: {integrity: sha512-GIh3usY1W3eVobx//OO9+Cwm+5evQBBdPGxDaeXwm25UqPMWRI240nXQA5F/5gL5Mwpf0DUC7DR2EmrKNQy+Rw==}
|
||||
peerDependencies:
|
||||
react: '>=17'
|
||||
@@ -1122,19 +1119,19 @@ packages:
|
||||
d3-zoom: 3.0.0
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.43)(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.45)(react@18.2.0)
|
||||
transitivePeerDependencies:
|
||||
- '@types/react'
|
||||
- immer
|
||||
dev: false
|
||||
|
||||
/@reactflow/minimap@11.7.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0):
|
||||
/@reactflow/minimap@11.7.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0):
|
||||
resolution: {integrity: sha512-kJEtyeQkTZYViLGebVWHVUJROMAGcvejvT+iX4DqKnFb5yK8E8LWlXQpRx2FrL9gDy80mJJaciy7IxnnQKE1bg==}
|
||||
peerDependencies:
|
||||
react: '>=17'
|
||||
react-dom: '>=17'
|
||||
dependencies:
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@types/d3-selection': 3.0.8
|
||||
'@types/d3-zoom': 3.0.6
|
||||
classcat: 5.0.4
|
||||
@@ -1142,41 +1139,41 @@ packages:
|
||||
d3-zoom: 3.0.0
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.43)(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.45)(react@18.2.0)
|
||||
transitivePeerDependencies:
|
||||
- '@types/react'
|
||||
- immer
|
||||
dev: false
|
||||
|
||||
/@reactflow/node-resizer@2.2.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0):
|
||||
/@reactflow/node-resizer@2.2.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0):
|
||||
resolution: {integrity: sha512-1Xb6q97uP7hRBLpog9sRCNfnsHdDgFRGEiU+lQqGgPEAeYwl4nRjWa/sXwH6ajniKxBhGEvrdzOgEFn6CRMcpQ==}
|
||||
peerDependencies:
|
||||
react: '>=17'
|
||||
react-dom: '>=17'
|
||||
dependencies:
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
classcat: 5.0.4
|
||||
d3-drag: 3.0.0
|
||||
d3-selection: 3.0.0
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.43)(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.45)(react@18.2.0)
|
||||
transitivePeerDependencies:
|
||||
- '@types/react'
|
||||
- immer
|
||||
dev: false
|
||||
|
||||
/@reactflow/node-toolbar@1.3.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0):
|
||||
/@reactflow/node-toolbar@1.3.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0):
|
||||
resolution: {integrity: sha512-JXDEuZ0wKjZ8z7qK2bIst0eZPzNyVEsiHL0e93EyuqT4fA9icoyE0fLq2ryNOOp7MXgId1h7LusnH6ta45F0yQ==}
|
||||
peerDependencies:
|
||||
react: '>=17'
|
||||
react-dom: '>=17'
|
||||
dependencies:
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
classcat: 5.0.4
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.43)(react@18.2.0)
|
||||
zustand: 4.4.7(@types/react@18.2.45)(react@18.2.0)
|
||||
transitivePeerDependencies:
|
||||
- '@types/react'
|
||||
- immer
|
||||
@@ -1331,7 +1328,7 @@ packages:
|
||||
defer-to-connect: 2.0.1
|
||||
dev: false
|
||||
|
||||
/@tailwindcss/typography@0.5.10(tailwindcss@3.3.6):
|
||||
/@tailwindcss/typography@0.5.10(tailwindcss@3.4.0):
|
||||
resolution: {integrity: sha512-Pe8BuPJQJd3FfRnm6H0ulKIGoMEQS+Vq01R6M5aCrFB/ccR/shT+0kXLjouGC1gFLm9hopTFN+DMP0pfwRWzPw==}
|
||||
peerDependencies:
|
||||
tailwindcss: '>=3.0.0 || insiders'
|
||||
@@ -1340,7 +1337,7 @@ packages:
|
||||
lodash.isplainobject: 4.0.6
|
||||
lodash.merge: 4.6.2
|
||||
postcss-selector-parser: 6.0.10
|
||||
tailwindcss: 3.3.6
|
||||
tailwindcss: 3.4.0
|
||||
dev: true
|
||||
|
||||
/@tootallnate/once@2.0.0:
|
||||
@@ -1660,14 +1657,14 @@ packages:
|
||||
resolution: {integrity: sha512-n1yyPsugYNSmHgxDFjicaI2+gCNjsBck8UX9kuofAKlc0h1bL+20oSF72KeNaW2DUlesbEVCFgyV2dPGTiY42g==}
|
||||
dev: false
|
||||
|
||||
/@types/react-dom@18.2.17:
|
||||
resolution: {integrity: sha512-rvrT/M7Df5eykWFxn6MYt5Pem/Dbyc1N8Y0S9Mrkw2WFCRiqUgw9P7ul2NpwsXCSM1DVdENzdG9J5SreqfAIWg==}
|
||||
/@types/react-dom@18.2.18:
|
||||
resolution: {integrity: sha512-TJxDm6OfAX2KJWJdMEVTwWke5Sc/E/RlnPGvGfS0W7+6ocy2xhDVQVh/KvC2Uf7kACs+gDytdusDSdWfWkaNzw==}
|
||||
dependencies:
|
||||
'@types/react': 18.2.43
|
||||
'@types/react': 18.2.45
|
||||
dev: false
|
||||
|
||||
/@types/react@18.2.43:
|
||||
resolution: {integrity: sha512-nvOV01ZdBdd/KW6FahSbcNplt2jCJfyWdTos61RYHV+FVv5L/g9AOX1bmbVcWcLFL8+KHQfh1zVIQrud6ihyQA==}
|
||||
/@types/react@18.2.45:
|
||||
resolution: {integrity: sha512-TtAxCNrlrBp8GoeEp1npd5g+d/OejJHFxS3OWmrPBMFaVQMSN0OFySozJio5BHxTuTeug00AVXVAjfDSfk+lUg==}
|
||||
dependencies:
|
||||
'@types/prop-types': 15.7.9
|
||||
'@types/scheduler': 0.16.5
|
||||
@@ -1696,7 +1693,7 @@ packages:
|
||||
resolution: {integrity: sha512-zuVdFrMJiuCDQUMCzQaD6KL28MjnqqN8XnAqiEq9PNm/hCPTSGfrXCOfwj1ow4LFb/tNymJPwsNbVePc1xFqrQ==}
|
||||
dev: false
|
||||
|
||||
/@vitejs/plugin-react@4.2.1(vite@5.0.7):
|
||||
/@vitejs/plugin-react@4.2.1(vite@5.0.10):
|
||||
resolution: {integrity: sha512-oojO9IDc4nCUUi8qIR11KoQm0XFFLIwsRBwHRR4d/88IWghn1y6ckz/bJ8GHDCsYEJee8mDzqtJxh15/cisJNQ==}
|
||||
engines: {node: ^14.18.0 || >=16.0.0}
|
||||
peerDependencies:
|
||||
@@ -1707,7 +1704,7 @@ packages:
|
||||
'@babel/plugin-transform-react-jsx-source': 7.23.3(@babel/core@7.23.5)
|
||||
'@types/babel__core': 7.20.5
|
||||
react-refresh: 0.14.0
|
||||
vite: 5.0.7
|
||||
vite: 5.0.10
|
||||
transitivePeerDependencies:
|
||||
- supports-color
|
||||
dev: false
|
||||
@@ -1867,14 +1864,14 @@ packages:
|
||||
typescript-esbuild: 0.3.1
|
||||
dev: false
|
||||
|
||||
/astro@4.0.3(typescript@5.2.2):
|
||||
resolution: {integrity: sha512-hrwe7CIVhSKW8/iibDs1hpqzZAtvx6Qu8TFFxjaGbooEWF720M9L+ZZtyTgrcy6K/ZHJ0xwFvZV3/X2Vvbf/LQ==}
|
||||
/astro@4.0.7(typescript@5.2.2):
|
||||
resolution: {integrity: sha512-K+Ms2AAQvi6yERPuglcI69tnHyTT44JCjzqprSjw3uOwFX7N9obpLgbhmLMH1fPFTgzt3ZD7APjmtDPN51makw==}
|
||||
engines: {node: '>=18.14.1', npm: '>=6.14.0'}
|
||||
hasBin: true
|
||||
dependencies:
|
||||
'@astrojs/compiler': 2.3.2
|
||||
'@astrojs/compiler': 2.3.4
|
||||
'@astrojs/internal-helpers': 0.2.1
|
||||
'@astrojs/markdown-remark': 4.0.0(astro@4.0.3)
|
||||
'@astrojs/markdown-remark': 4.0.1
|
||||
'@astrojs/telemetry': 3.0.4
|
||||
'@babel/core': 7.23.5
|
||||
'@babel/generator': 7.23.5
|
||||
@@ -1913,7 +1910,7 @@ packages:
|
||||
mime: 3.0.0
|
||||
ora: 7.0.1
|
||||
p-limit: 5.0.0
|
||||
p-queue: 7.4.1
|
||||
p-queue: 8.0.1
|
||||
path-to-regexp: 6.2.1
|
||||
preferred-pm: 3.1.2
|
||||
probe-image-size: 7.2.3
|
||||
@@ -1928,8 +1925,8 @@ packages:
|
||||
tsconfck: 3.0.0(typescript@5.2.2)
|
||||
unist-util-visit: 5.0.0
|
||||
vfile: 6.0.1
|
||||
vite: 5.0.7
|
||||
vitefu: 0.2.5(vite@5.0.7)
|
||||
vite: 5.0.10
|
||||
vitefu: 0.2.5(vite@5.0.10)
|
||||
which-pm: 2.1.1
|
||||
yargs-parser: 21.1.1
|
||||
zod: 3.22.4
|
||||
@@ -1955,7 +1952,7 @@ packages:
|
||||
resolution: {integrity: sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==}
|
||||
dev: true
|
||||
|
||||
/autoprefixer@10.4.16(postcss@8.4.31):
|
||||
/autoprefixer@10.4.16(postcss@8.4.32):
|
||||
resolution: {integrity: sha512-7vd3UC6xKp0HLfua5IjZlcXvGAGy7cBAXTg2lyQ/8WpNhd6SiZ8Be+xm3FyBSYJx5GKcpRCzBh7RH4/0dnY+uQ==}
|
||||
engines: {node: ^10 || ^12 || >=14}
|
||||
hasBin: true
|
||||
@@ -1967,7 +1964,7 @@ packages:
|
||||
fraction.js: 4.3.7
|
||||
normalize-range: 0.1.2
|
||||
picocolors: 1.0.0
|
||||
postcss: 8.4.31
|
||||
postcss: 8.4.32
|
||||
postcss-value-parser: 4.2.0
|
||||
dev: false
|
||||
|
||||
@@ -2913,6 +2910,7 @@ packages:
|
||||
glob-parent: 5.1.2
|
||||
merge2: 1.4.1
|
||||
micromatch: 4.0.5
|
||||
dev: false
|
||||
|
||||
/fast-glob@3.3.2:
|
||||
resolution: {integrity: sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==}
|
||||
@@ -2923,7 +2921,6 @@ packages:
|
||||
glob-parent: 5.1.2
|
||||
merge2: 1.4.1
|
||||
micromatch: 4.0.5
|
||||
dev: false
|
||||
|
||||
/fast-memoize@2.5.2:
|
||||
resolution: {integrity: sha512-Ue0LwpDYErFbmNnZSF0UH6eImUwDmogUO1jyE+JbN2gsQz/jICm1Ve7t9QT0rNSsfJt+Hs4/S3GnsDVjL4HVrw==}
|
||||
@@ -3137,8 +3134,8 @@ packages:
|
||||
engines: {node: '>=16'}
|
||||
dev: false
|
||||
|
||||
/gh-pages@6.1.0:
|
||||
resolution: {integrity: sha512-MdXigvqN3I66Y+tAZsQJMzpBWQOI1snD6BYuECmP+GEdryYMMOQvzn4AConk/+qNg/XIuQhB1xNGrl3Rmj1iow==}
|
||||
/gh-pages@6.1.1:
|
||||
resolution: {integrity: sha512-upnohfjBwN5hBP9w2dPE7HO5JJTHzSGMV1JrLrHvNuqmjoYHg6TBrCcnEoorjG/e0ejbuvnwyKMdTyM40PEByw==}
|
||||
engines: {node: '>=10'}
|
||||
hasBin: true
|
||||
dependencies:
|
||||
@@ -4023,8 +4020,8 @@ packages:
|
||||
engines: {node: '>=12'}
|
||||
dev: false
|
||||
|
||||
/lucide-react@0.294.0(react@18.2.0):
|
||||
resolution: {integrity: sha512-V7o0/VECSGbLHn3/1O67FUgBwWB+hmzshrgDVRJQhMh8uj5D3HBuIvhuAmQTtlupILSplwIZg5FTc4tTKMA2SA==}
|
||||
/lucide-react@0.300.0(react@18.2.0):
|
||||
resolution: {integrity: sha512-rQxUUCmWAvNLoAsMZ5j04b2+OJv6UuNLYMY7VK0eVlm4aTwUEjEEHc09/DipkNIlhXUSDn2xoyIzVT0uh7dRsg==}
|
||||
peerDependencies:
|
||||
react: ^16.5.1 || ^17.0.0 || ^18.0.0
|
||||
dependencies:
|
||||
@@ -4672,16 +4669,10 @@ packages:
|
||||
object-assign: 4.1.1
|
||||
thenify-all: 1.6.0
|
||||
|
||||
/nanoid@3.3.6:
|
||||
resolution: {integrity: sha512-BGcqMMJuToF7i1rt+2PWSNVnWIkGCU78jBG3RxO/bZlnZPK2Cmi2QaffxGO/2RvWi9sL+FAiRiXMgsyxQ1DIDA==}
|
||||
engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
|
||||
hasBin: true
|
||||
|
||||
/nanoid@3.3.7:
|
||||
resolution: {integrity: sha512-eSRppjcPIatRIMC1U6UngP8XFcz8MQWGQdt1MTBQ7NaAmvXDfvNxbvWV3x2y6CdEUciCSsDHDQZbhYaB8QEo2g==}
|
||||
engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
|
||||
hasBin: true
|
||||
dev: false
|
||||
|
||||
/nanoid@5.0.4:
|
||||
resolution: {integrity: sha512-vAjmBf13gsmhXSgBrtIclinISzFFy22WwCYoyilZlsrRXNIHSwgFQ1bEdjRwMT3aoadeIF6HMuDRlOxzfXV8ig==}
|
||||
@@ -4826,8 +4817,8 @@ packages:
|
||||
npm-normalize-package-bin: 3.0.1
|
||||
dev: false
|
||||
|
||||
/npm-check-updates@16.14.11:
|
||||
resolution: {integrity: sha512-0MMWGbGci22Pu77bR9jRsy5qgxdQSJVqNtSyyFeubDPtbcU36z4gjEDITu26PMabFWPNkAoVfKF31M3uKUvzFg==}
|
||||
/npm-check-updates@16.14.12:
|
||||
resolution: {integrity: sha512-5FvqaDX8AqWWTDQFbBllgLwoRXTvzlqVIRSKl9Kg8bYZTfNwMnrp1Zlmb5e/ocf11UjPTc+ShBFjYQ7kg6FL0w==}
|
||||
engines: {node: '>=14.14'}
|
||||
hasBin: true
|
||||
dependencies:
|
||||
@@ -4972,8 +4963,8 @@ packages:
|
||||
mimic-fn: 4.0.0
|
||||
dev: false
|
||||
|
||||
/openai@4.20.1:
|
||||
resolution: {integrity: sha512-Dd3q8EvINfganZFtg6V36HjrMaihqRgIcKiHua4Nq9aw/PxOP48dhbsk8x5klrxajt5Lpnc1KTOG5i1S6BKAJA==}
|
||||
/openai@4.24.1:
|
||||
resolution: {integrity: sha512-ezm/O3eiZMnyBqirUnWm9N6INJU1WhNtz+nK/Zj/2oyKvRz9pgpViDxa5wYOtyGYXPn1sIKBV0I/S4BDhtydqw==}
|
||||
hasBin: true
|
||||
dependencies:
|
||||
'@types/node': 18.18.6
|
||||
@@ -5049,17 +5040,17 @@ packages:
|
||||
aggregate-error: 3.1.0
|
||||
dev: false
|
||||
|
||||
/p-queue@7.4.1:
|
||||
resolution: {integrity: sha512-vRpMXmIkYF2/1hLBKisKeVYJZ8S2tZ0zEAmIJgdVKP2nq0nh4qCdf8bgw+ZgKrkh71AOCaqzwbJJk1WtdcF3VA==}
|
||||
engines: {node: '>=12'}
|
||||
/p-queue@8.0.1:
|
||||
resolution: {integrity: sha512-NXzu9aQJTAzbBqOt2hwsR63ea7yvxJc0PwN/zobNAudYfb1B7R08SzB4TsLeSbUCuG467NhnoT0oO6w1qRO+BA==}
|
||||
engines: {node: '>=18'}
|
||||
dependencies:
|
||||
eventemitter3: 5.0.1
|
||||
p-timeout: 5.1.0
|
||||
p-timeout: 6.1.2
|
||||
dev: false
|
||||
|
||||
/p-timeout@5.1.0:
|
||||
resolution: {integrity: sha512-auFDyzzzGZZZdHz3BtET9VEz0SE/uMEAx7uWfGPucfzEwwe/xH0iVeZibQmANYE/hp9T2+UUZT5m+BKyrDp3Ew==}
|
||||
engines: {node: '>=12'}
|
||||
/p-timeout@6.1.2:
|
||||
resolution: {integrity: sha512-UbD77BuZ9Bc9aABo74gfXhNvzC9Tx7SxtHSh1fxvx3jTLLYvmVhiQZZrJzqqU0jKbN32kb5VOKiLEQI/3bIjgQ==}
|
||||
engines: {node: '>=14.16'}
|
||||
dev: false
|
||||
|
||||
/p-try@2.2.0:
|
||||
@@ -5230,27 +5221,27 @@ packages:
|
||||
fsevents: 2.3.2
|
||||
dev: true
|
||||
|
||||
/postcss-import@15.1.0(postcss@8.4.31):
|
||||
/postcss-import@15.1.0(postcss@8.4.32):
|
||||
resolution: {integrity: sha512-hpr+J05B2FVYUAXHeK1YyI267J/dDDhMU6B6civm8hSY1jYJnBXxzKDKDswzJmtLHryrjhnDjqqp/49t8FALew==}
|
||||
engines: {node: '>=14.0.0'}
|
||||
peerDependencies:
|
||||
postcss: ^8.0.0
|
||||
dependencies:
|
||||
postcss: 8.4.31
|
||||
postcss: 8.4.32
|
||||
postcss-value-parser: 4.2.0
|
||||
read-cache: 1.0.0
|
||||
resolve: 1.22.8
|
||||
|
||||
/postcss-js@4.0.1(postcss@8.4.31):
|
||||
/postcss-js@4.0.1(postcss@8.4.32):
|
||||
resolution: {integrity: sha512-dDLF8pEO191hJMtlHFPRa8xsizHaM82MLfNkUHdUtVEV3tgTp5oj+8qbEqYM57SLfc74KSbw//4SeJma2LRVIw==}
|
||||
engines: {node: ^12 || ^14 || >= 16}
|
||||
peerDependencies:
|
||||
postcss: ^8.4.21
|
||||
dependencies:
|
||||
camelcase-css: 2.0.1
|
||||
postcss: 8.4.31
|
||||
postcss: 8.4.32
|
||||
|
||||
/postcss-load-config@4.0.2(postcss@8.4.31):
|
||||
/postcss-load-config@4.0.2(postcss@8.4.32):
|
||||
resolution: {integrity: sha512-bSVhyJGL00wMVoPUzAVAnbEoWyqRxkjv64tUl427SKnPrENtq6hJwUojroMz2VB+Q1edmi4IfrAPpami5VVgMQ==}
|
||||
engines: {node: '>= 14'}
|
||||
peerDependencies:
|
||||
@@ -5263,16 +5254,16 @@ packages:
|
||||
optional: true
|
||||
dependencies:
|
||||
lilconfig: 3.0.0
|
||||
postcss: 8.4.31
|
||||
postcss: 8.4.32
|
||||
yaml: 2.3.4
|
||||
|
||||
/postcss-nested@6.0.1(postcss@8.4.31):
|
||||
/postcss-nested@6.0.1(postcss@8.4.32):
|
||||
resolution: {integrity: sha512-mEp4xPMi5bSWiMbsgoPfcP74lsWLHkQbZc3sY+jWYd65CUwXrUaTp0fmNpa01ZcETKlIgUdFN/MpS2xZtqL9dQ==}
|
||||
engines: {node: '>=12.0'}
|
||||
peerDependencies:
|
||||
postcss: ^8.2.14
|
||||
dependencies:
|
||||
postcss: 8.4.31
|
||||
postcss: 8.4.32
|
||||
postcss-selector-parser: 6.0.13
|
||||
|
||||
/postcss-selector-parser@6.0.10:
|
||||
@@ -5293,14 +5284,6 @@ packages:
|
||||
/postcss-value-parser@4.2.0:
|
||||
resolution: {integrity: sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==}
|
||||
|
||||
/postcss@8.4.31:
|
||||
resolution: {integrity: sha512-PS08Iboia9mts/2ygV3eLpY5ghnUcfLV/EXTOW1E2qYxJKGGBUtNjN76FYHnMs36RmARn41bC0AZmn+rR0OVpQ==}
|
||||
engines: {node: ^10 || ^12 || >=14}
|
||||
dependencies:
|
||||
nanoid: 3.3.6
|
||||
picocolors: 1.0.0
|
||||
source-map-js: 1.0.2
|
||||
|
||||
/postcss@8.4.32:
|
||||
resolution: {integrity: sha512-D/kj5JNu6oo2EIy+XL/26JEDTlIbB8hw85G8StOE6L74RQAVVP5rej6wxCNqyMbR4RkPfqvezVbPw81Ngd6Kcw==}
|
||||
engines: {node: ^10 || ^12 || >=14}
|
||||
@@ -5308,7 +5291,6 @@ packages:
|
||||
nanoid: 3.3.7
|
||||
picocolors: 1.0.0
|
||||
source-map-js: 1.0.2
|
||||
dev: false
|
||||
|
||||
/prebuild-install@7.1.1:
|
||||
resolution: {integrity: sha512-jAXscXWMcCK8GgCoHOfIr0ODh5ai8mj63L2nWrjuAgXE6tDyYGnx4/8o/rCgU+B4JSyZBKbeZqzhtwtC3ovxjw==}
|
||||
@@ -5344,11 +5326,11 @@ packages:
|
||||
engines: {node: ^14.15.0 || >=16.0.0}
|
||||
dependencies:
|
||||
'@astrojs/compiler': 1.8.2
|
||||
prettier: 3.1.0
|
||||
prettier: 3.1.1
|
||||
sass-formatter: 0.7.8
|
||||
dev: true
|
||||
|
||||
/prettier-plugin-tailwindcss@0.5.9(prettier-plugin-astro@0.12.2)(prettier@3.1.0):
|
||||
/prettier-plugin-tailwindcss@0.5.9(prettier-plugin-astro@0.12.2)(prettier@3.1.1):
|
||||
resolution: {integrity: sha512-9x3t1s2Cjbut2QiP+O0mDqV3gLXTe2CgRlQDgucopVkUdw26sQi53p/q4qvGxMLBDfk/dcTV57Aa/zYwz9l8Ew==}
|
||||
engines: {node: '>=14.21.3'}
|
||||
peerDependencies:
|
||||
@@ -5397,12 +5379,12 @@ packages:
|
||||
prettier-plugin-twig-melody:
|
||||
optional: true
|
||||
dependencies:
|
||||
prettier: 3.1.0
|
||||
prettier: 3.1.1
|
||||
prettier-plugin-astro: 0.12.2
|
||||
dev: true
|
||||
|
||||
/prettier@3.1.0:
|
||||
resolution: {integrity: sha512-TQLvXjq5IAibjh8EpBIkNKxO749UEWABoiIZehEPiY4GNpVdhaFKqSTu+QrlU6D2dPAfubRmtJTi4K4YkQ5eXw==}
|
||||
/prettier@3.1.1:
|
||||
resolution: {integrity: sha512-22UbSzg8luF4UuZtzgiUOfcGM8s4tjBv6dJRT7j275NXsy2jb4aJa4NNveul5x4eqlF1wuhuR2RElK71RvmVaw==}
|
||||
engines: {node: '>=14'}
|
||||
hasBin: true
|
||||
dev: true
|
||||
@@ -5557,18 +5539,18 @@ packages:
|
||||
loose-envify: 1.4.0
|
||||
dev: false
|
||||
|
||||
/reactflow@11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0):
|
||||
/reactflow@11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0):
|
||||
resolution: {integrity: sha512-Q616fElAc5/N37tMwjuRkkgm/VgmnLLTNNCj61z5mvJxae+/VXZQMfot1K6a5LLz9G3SVKqU97PMb9Ga1PRXew==}
|
||||
peerDependencies:
|
||||
react: '>=17'
|
||||
react-dom: '>=17'
|
||||
dependencies:
|
||||
'@reactflow/background': 11.3.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/controls': 11.2.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/minimap': 11.7.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/node-resizer': 2.2.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/node-toolbar': 1.3.6(@types/react@18.2.43)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/background': 11.3.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/controls': 11.2.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/core': 11.10.1(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/minimap': 11.7.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/node-resizer': 2.2.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
'@reactflow/node-toolbar': 1.3.6(@types/react@18.2.45)(react-dom@18.2.0)(react@18.2.0)
|
||||
react: 18.2.0
|
||||
react-dom: 18.2.0(react@18.2.0)
|
||||
transitivePeerDependencies:
|
||||
@@ -6284,14 +6266,14 @@ packages:
|
||||
picocolors: 1.0.0
|
||||
dev: false
|
||||
|
||||
/tailwind-merge@2.1.0:
|
||||
resolution: {integrity: sha512-l11VvI4nSwW7MtLSLYT4ldidDEUwQAMWuSHk7l4zcXZDgnCRa0V3OdCwFfM7DCzakVXMNRwAeje9maFFXT71dQ==}
|
||||
/tailwind-merge@2.2.0:
|
||||
resolution: {integrity: sha512-SqqhhaL0T06SW59+JVNfAqKdqLs0497esifRrZ7jOaefP3o64fdFNDMrAQWZFMxTLJPiHVjRLUywT8uFz1xNWQ==}
|
||||
dependencies:
|
||||
'@babel/runtime': 7.23.5
|
||||
dev: false
|
||||
|
||||
/tailwindcss@3.3.6:
|
||||
resolution: {integrity: sha512-AKjF7qbbLvLaPieoKeTjG1+FyNZT6KaJMJPFeQyLfIp7l82ggH1fbHJSsYIvnbTFQOlkh+gBYpyby5GT1LIdLw==}
|
||||
/tailwindcss@3.4.0:
|
||||
resolution: {integrity: sha512-VigzymniH77knD1dryXbyxR+ePHihHociZbXnLZHUyzf2MMs2ZVqlUrZ3FvpXP8pno9JzmILt1sZPD19M3IxtA==}
|
||||
engines: {node: '>=14.0.0'}
|
||||
hasBin: true
|
||||
dependencies:
|
||||
@@ -6300,7 +6282,7 @@ packages:
|
||||
chokidar: 3.5.3
|
||||
didyoumean: 1.2.2
|
||||
dlv: 1.1.3
|
||||
fast-glob: 3.3.1
|
||||
fast-glob: 3.3.2
|
||||
glob-parent: 6.0.2
|
||||
is-glob: 4.0.3
|
||||
jiti: 1.20.0
|
||||
@@ -6309,11 +6291,11 @@ packages:
|
||||
normalize-path: 3.0.0
|
||||
object-hash: 3.0.0
|
||||
picocolors: 1.0.0
|
||||
postcss: 8.4.31
|
||||
postcss-import: 15.1.0(postcss@8.4.31)
|
||||
postcss-js: 4.0.1(postcss@8.4.31)
|
||||
postcss-load-config: 4.0.2(postcss@8.4.31)
|
||||
postcss-nested: 6.0.1(postcss@8.4.31)
|
||||
postcss: 8.4.32
|
||||
postcss-import: 15.1.0(postcss@8.4.32)
|
||||
postcss-js: 4.0.1(postcss@8.4.32)
|
||||
postcss-load-config: 4.0.2(postcss@8.4.32)
|
||||
postcss-nested: 6.0.1(postcss@8.4.32)
|
||||
postcss-selector-parser: 6.0.13
|
||||
resolve: 1.22.8
|
||||
sucrase: 3.34.0
|
||||
@@ -6798,8 +6780,8 @@ packages:
|
||||
vfile-message: 4.0.2
|
||||
dev: false
|
||||
|
||||
/vite@5.0.7:
|
||||
resolution: {integrity: sha512-B4T4rJCDPihrQo2B+h1MbeGL/k/GMAHzhQ8S0LjQ142s6/+l3hHTT095ORvsshj4QCkoWu3Xtmob5mazvakaOw==}
|
||||
/vite@5.0.10:
|
||||
resolution: {integrity: sha512-2P8J7WWgmc355HUMlFrwofacvr98DAjoE52BfdbwQtyLH06XKwaL/FMnmKM2crF0iX4MpmMKoDlNCB1ok7zHCw==}
|
||||
engines: {node: ^18.0.0 || >=20.0.0}
|
||||
hasBin: true
|
||||
peerDependencies:
|
||||
@@ -6833,7 +6815,7 @@ packages:
|
||||
fsevents: 2.3.3
|
||||
dev: false
|
||||
|
||||
/vitefu@0.2.5(vite@5.0.7):
|
||||
/vitefu@0.2.5(vite@5.0.10):
|
||||
resolution: {integrity: sha512-SgHtMLoqaeeGnd2evZ849ZbACbnwQCIwRH57t18FxcXoZop0uQu0uzlIhJBlF/eWVzuce0sHeqPcDo+evVcg8Q==}
|
||||
peerDependencies:
|
||||
vite: ^3.0.0 || ^4.0.0 || ^5.0.0
|
||||
@@ -6841,7 +6823,7 @@ packages:
|
||||
vite:
|
||||
optional: true
|
||||
dependencies:
|
||||
vite: 5.0.7
|
||||
vite: 5.0.10
|
||||
dev: false
|
||||
|
||||
/vscode-oniguruma@1.7.0:
|
||||
@@ -6993,7 +6975,7 @@ packages:
|
||||
resolution: {integrity: sha512-iC+8Io04lddc+mVqQ9AZ7OQ2MrUKGN+oIQyq1vemgt46jwCwLfhq7/pwnBnNXXXZb8VTVLKwp9EDkx+ryxIWmg==}
|
||||
dev: false
|
||||
|
||||
/zustand@4.4.7(@types/react@18.2.43)(react@18.2.0):
|
||||
/zustand@4.4.7(@types/react@18.2.45)(react@18.2.0):
|
||||
resolution: {integrity: sha512-QFJWJMdlETcI69paJwhSMJz7PPWjVP8Sjhclxmxmxv/RYI7ZOvR5BHX+ktH0we9gTWQMxcne8q1OY8xxz604gw==}
|
||||
engines: {node: '>=12.7.0'}
|
||||
peerDependencies:
|
||||
@@ -7008,7 +6990,7 @@ packages:
|
||||
react:
|
||||
optional: true
|
||||
dependencies:
|
||||
'@types/react': 18.2.43
|
||||
'@types/react': 18.2.45
|
||||
react: 18.2.0
|
||||
use-sync-external-store: 1.2.0(react@18.2.0)
|
||||
dev: false
|
||||
|
||||
BIN
public/guides/backend-languages/back-vs-front.png
Normal file
BIN
public/guides/backend-languages/back-vs-front.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 119 KiB |
BIN
public/guides/backend-languages/backend-roadmap-part.png
Normal file
BIN
public/guides/backend-languages/backend-roadmap-part.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 80 KiB |
BIN
public/guides/backend-languages/javascript-interest.png
Normal file
BIN
public/guides/backend-languages/javascript-interest.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 99 KiB |
BIN
public/guides/backend-languages/pypl-go-index.png
Normal file
BIN
public/guides/backend-languages/pypl-go-index.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 48 KiB |
Binary file not shown.
@@ -13,7 +13,7 @@ const { frontmatter, id } = guide;
|
||||
class:list={[
|
||||
"block no-underline py-2 group text-md items-center text-gray-600 hover:text-blue-600 flex justify-between border-b",
|
||||
]}
|
||||
href={`/guides/${id}`}
|
||||
href={frontmatter.excludedBySlug ? frontmatter.excludedBySlug : `/guides/${id}`}
|
||||
>
|
||||
<span class="group-hover:translate-x-2 transition-transform">
|
||||
{frontmatter.title}
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<div
|
||||
class='prose-xl prose-blockquote:font-normal prose container prose-code:bg-transparent prose-h2:text-3xl prose-h2:mt-10 prose-h2:mb-3 prose-h3:mt-2 prose-img:mt-1'
|
||||
class='prose-xl prose-blockquote:font-normal prose container prose-code:bg-transparent prose-h2:text-3xl prose-h2:mt-10 prose-h2:mb-3 prose-h5:font-medium prose-h3:mt-2 prose-img:mt-1'
|
||||
>
|
||||
<slot />
|
||||
</div>
|
||||
|
||||
@@ -2,4 +2,4 @@
|
||||
|
||||
> Servers are ephemeral, you don't care about them. You only care about the service as a whole.
|
||||
|
||||
If a single server dies, it should be of no big concern to you. This is where the real benefit of AWS comes in compared to using physical servers yourself. Normally if a physical server dies, there's panic. With AWS, you don't care, because auto-scaling will give you a fresh new instance soon anyway. Netflix have taken this several steps further with their [simian army](http://techblog.netflix.com/2011/07/netflix-simian-army.html), where they have things like [Chaos Monkey](http://techblog.netflix.com/2012/07/chaos-monkey-released-into-wild.html), which will kill random instances in production (they also have Chaos Gorilla to kill AZs and I've heard rumour of a Chaos Kong to kill regions...). The point is that servers will fail, but this shouldn't matter in your application.
|
||||
If a single server dies, it should be of no big concern to you. This is where the real benefit of AWS comes in compared to using physical servers yourself. Normally if a physical server dies, there's panic. With AWS, you don't care, because auto-scaling will give you a fresh new instance soon anyway. Netflix have taken this several steps further with their [simian army](http://techblog.netflix.com/2011/07/netflix-simian-army.html), where they have things like [Chaos Monkey](https://github.com/netflix/chaosmonkey), which will kill random instances in production (they also have Chaos Gorilla to kill AZs and I've heard rumour of a Chaos Kong to kill regions...). The point is that servers will fail, but this shouldn't matter in your application.
|
||||
|
||||
@@ -37,7 +37,7 @@
|
||||
- [The Web Performance impact of jQuery](https://twitter.com/TheRealNooshu/status/1509487050122276864)
|
||||
- [Have Single-Page Apps Ruined the Web? | Transitional Apps](https://www.youtube.com/watch?v=860d8usGC0o)
|
||||
- [Improve how you architect webapps](https://www.patterns.dev/)
|
||||
- [Nuxt SSR Optimizing Tips](https://vueschool.io/articles/vuejs-tutorials/nuxt-ssr-optimizing-tips/, Filip Rakowski
|
||||
- [Nuxt SSR Optimizing Tips](https://vueschool.io/articles/vuejs-tutorials/nuxt-ssr-optimizing-tips/), Filip Rakowski
|
||||
- [GPU accelerated JavaScript](https://gpu.rocks/#/)
|
||||
- [Introducing Partytown 🎉: Run Third-Party Scripts From a Web Worker](https://dev.to/adamdbradley/introducing-partytown-run-third-party-scripts-from-a-web-worker-2cnp)
|
||||
- [Astro: Astro is a fresh but familiar approach to building websites. Astro combines decades of proven performance best practices with the DX improvements of the component-oriented era. Use your favorite JavaScript framework and automatically ship the bare-minimum amount of JavaScript—by default.](https://docs.astro.build/getting-started/)
|
||||
@@ -71,7 +71,7 @@
|
||||
- [Idle Until Urgent](https://philipwalton.com/articles/idle-until-urgent/)
|
||||
- [Browser painting and considerations for web performance](https://css-tricks.com/browser-painting-and-considerations-for-web-performance/)
|
||||
- [The Cost Of JavaScript In 2018](https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4) ([Video](https://www.youtube.com/watch?v=i5R7giitymk))
|
||||
- [Examining Web Worker Performance](https://www.loxodrome.io/post/web-worker-performance/)
|
||||
- [Examining Web Worker Performance](https://www.jameslmilner.com/posts/web-worker-performance)
|
||||
- [Front-End Performance Checklist](https://github.com/thedaviddias/Front-End-Performance-Checklist)
|
||||
- [jankfree](http://jankfree.org/)
|
||||
- [What forces layout/reflow?](https://gist.github.com/paulirish/5d52fb081b3570c81e3a)
|
||||
|
||||
394
src/data/guides/backend-languages.md
Normal file
394
src/data/guides/backend-languages.md
Normal file
@@ -0,0 +1,394 @@
|
||||
---
|
||||
title: 'The 5 Best Backend Development Languages to Master (2024)'
|
||||
description: 'Discover the best backend development languages to master in 2024.'
|
||||
author:
|
||||
name: 'Kamran Ahmed'
|
||||
url: 'https://twitter.com/kamrify'
|
||||
imageUrl: '/authors/kamranahmedse.jpeg'
|
||||
excludedBySlug: '/backend/languages'
|
||||
seo:
|
||||
title: 'The 5 Best Backend Development Languages to Master (2024)'
|
||||
description: 'Discover the best backend development languages to learn right now for career development, with practical tips from an experienced developer.'
|
||||
isNew: true
|
||||
type: 'textual'
|
||||
date: 2024-01-18
|
||||
sitemap:
|
||||
priority: 0.7
|
||||
changefreq: 'weekly'
|
||||
tags:
|
||||
- 'guide'
|
||||
- 'textual-guide'
|
||||
- 'guide-sitemap'
|
||||
---
|
||||
|
||||
Web development is typically divided into two main categories: [backend development](https://roadmap.sh/backend) and [frontend development](https://roadmap.sh/frontend). Frontend development focuses on the visible part of the application for end-users, i.e. the part that users interact with, while backend development involves writing code that remains unseen but is essential for the functioning of all applications—the business logic.
|
||||
|
||||
Two of the key components when it comes to backend development are the programming language that you are going to code in and the database. In this article, we will be looking into a subset of programming languages that could be used for backend development. We will be discussing the pros and cons of each and the community to help you pick the best programming language for backend development.
|
||||
|
||||
Without further ado, let’s get started!
|
||||
|
||||
## What are backend languages?
|
||||
|
||||
When it comes to web development, there is a very clear distinction between frontend and backend technologies.
|
||||
|
||||
While the frontend ecosystem is quite limited to JavaScript (and other JavaScript-based languages, like TypeScript) due to Browser compatibility, the backend (A.K.A server-side) is a very different scenario.
|
||||
|
||||

|
||||
|
||||
Please note that neither of those lists is extensive, as they’re both constantly growing.
|
||||
|
||||
You can think of a backend language as one that “runs on the server side”. That said, by that definition, any language is a backend language because even JavaScript nowadays can be used on the backend as well (thanks to Node, Bun, and Deno).
|
||||
|
||||
However, we can go one step further and say:
|
||||
|
||||
> “A backend language is a server side programming language that has the tools and frameworks required to build web backends”
|
||||
|
||||
That will narrow down the list a little bit. But essentially, we can think of backend languages as anything that fits the following list:
|
||||
|
||||
- Is able to listen for incoming HTTP/S connections.
|
||||
- Can access databases.
|
||||
- Can send HTTP/S requests.
|
||||
- Can access the filesystem.
|
||||
- Has a rich ecosystem of tools and frameworks to build web applications.
|
||||
|
||||
With those features and a rich ecosystem of libraries and frameworks, a language can definitely be considered “backend-ready”.
|
||||
|
||||
## Why learn a backend programming language?
|
||||
|
||||
If you’re already a backend developer, then the main reason would be to become a more versatile developer. The more languages you know, the better code you’ll write. Either because you’ve learned different ways of solving the same problem, or simply because you’ll be able to contribute to more projects.
|
||||
|
||||
If, on the other hand, you’re just getting started, the main reason would be that you’re entering an industry that’s always looking for people.
|
||||
|
||||
## Is the market in demand for backend developers?
|
||||
|
||||
One thing to keep in mind right now is that the software development market is always in demand for devs. For example, the [U.S. Bureau of Labor Statistics gives our industry a 25% growth rate](https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm) (demand-wise) from 2022 to 2023, whereas the mean for other industries is 3%.
|
||||
|
||||
According to [JetBrains, during 2022, 75% of developers were involved with web development](https://www.jetbrains.com/lp/devecosystem-2022/) in one fashion or another, so whether you’re backend devs or frontend devs, there is always someone looking for you.
|
||||
|
||||
That said, we also have to consider that this industry is becoming a global industry. While some countries might still be fighting that process back, most developers can directly access the global market and work for any company in the world.
|
||||
|
||||
That is a great opportunity for a backend developer who lives in an area where there isn’t a big IT industry; however, it also means competing with every other developer in the world. That might cause the illusion that the IT industry is in recession or that there are no job opportunities for developers.
|
||||
|
||||
There are always opportunities; it’s just that you're now after the same job that many others from around the world are after as well.
|
||||
|
||||
That said, backend devs are always in high demand because they’re the bread and butter of any web application. They’re always required to create the underlying platform that will power most systems, so the key to standing out here is to stay up-to-date with the industry’s trends and technologies.
|
||||
|
||||
Don’t get me wrong. You can’t possibly be expected to keep up with every single programming language that is released or with all the new frameworks that are created every month. However, keeping an eye on the industry and understanding what survives long enough to become a new industry standard is important. You have to keep updating yourself and learning new technologies/skills constantly; that way, you’ll stay relevant.
|
||||
|
||||
## Is learning a backend language good for your career?
|
||||
|
||||
Whether you’re a frontend developer looking to become full-stack (someone who can code both the backend and the frontend of an application), or if you’re new to the industry and you’re thinking if this might be the best place for you, the answer is “yes”.
|
||||
|
||||
Backend developers are always in demand, so adding a new tool to your already existing toolbelt (if you’re already a dev) will only make you more flexible in the eyes of your employer.
|
||||
|
||||
But remember, a language is just a language until you give it context. If you’re wondering whether or not one of the backend languages in this article might be for you, the answer will always be “yes”. However, understand that if backend development is new to you, you will also need to pick up other skills and backend technologies around the language, such as:
|
||||
|
||||
- Understanding HTTP.
|
||||
- Learning Structured Query Language (SQL) to query your databases.
|
||||
- Understanding how APIs work.
|
||||
- What server side rendering means and how to take advantage of it.
|
||||
- What web servers are and how to use them/build them.
|
||||
|
||||
Otherwise, you’ll understand the language, but you won’t know how to use it for the role of backend development.
|
||||
|
||||
## Top 5 Backend Languages to Learn for Web Development
|
||||
|
||||
With that introduction out of the way, let’s see the top 5 backend programming languages that you might want to learn if you’re looking to broaden your horizons in the server-side world.
|
||||
The languages we’ll cover are:
|
||||
|
||||
- Python
|
||||
- Java
|
||||
- JavaScript
|
||||
- PHP
|
||||
- Go
|
||||
|
||||
Why these languages specifically?
|
||||
|
||||
They’re some of the most known and used languages in the industry right now (see [StackOverflow’s 2023 Developer Survey](https://survey.stackoverflow.co/2023/#most-popular-technologies-language-prof)). That said, keep in mind that these are all great options, and they’re not presented here in any particular order.
|
||||
|
||||
### Python
|
||||
|
||||
Python has been around for decades already and while it’s never been the most popular option, it has always managed to stay within the top 5 choices. People love it for being easy to read, straightforward, and able to handle all sorts of tasks, making it a top pick for developers globally. Sure, Python's got a big name in data processing and machine learning, but let's not forget its solid impact on web development!.
|
||||
|
||||
What makes Python extra appealing, especially for beginners, is the fact that reading and writing it feels very much like English (or at least, as pseudo code). This makes it a top choice for folks just starting out in coding.
|
||||
|
||||
#### Beginner Accessibility and Learning Resources
|
||||
|
||||
One of Python's standout features is its beginner-friendly syntax, making it an ideal language for those new to programming. The emphasis on readability and the absence of complex syntax (for the most part), eases the learning curve, enabling new developers to quickly grasp fundamental concepts.
|
||||
|
||||
Python's community plays a critical role in its accessibility. Abundant learning resources, tutorials, and documentation are readily available, empowering beginners to progress from basic programming principles to advanced backend development seamlessly. Online platforms like Codecademy, Coursera, realpython.com, and even Google offer comprehensive courses tailored to all skill levels.
|
||||
|
||||
#### Practical Applications and Popular Frameworks
|
||||
|
||||
Python's versatility is evident in its applicability across a spectrum of industries, from web development and data science to artificial intelligence and automation. In the context of backend development, Python shines brightly with its two standout frameworks: [Django](https://www.djangoproject.com/) and [Flask](https://github.com/pallets/flask).
|
||||
|
||||
##### Django
|
||||
|
||||
So, let's talk about Django – it's like the superhero of web frameworks, at least in the world of Python. This high-level powerhouse is all about that "batteries-included" style, giving you a whole package of tools and features that make development lightning-fast. It follows the [Model-View-Controller](https://www.crio.do/blog/understand-mvc-architecture/) (MVC) architecture that gives your web applications a solid structure, making them scalable and easy to keep up.
|
||||
|
||||
Part of that whole “batteries-included” motto means that it comes with an admin panel, an [ORM](https://www.freecodecamp.org/news/what-is-an-orm-the-meaning-of-object-relational-mapping-database-tools/) (Object-Relational Mapping) for smooth data handling, and security features that make sure your project is secured out-of-the-box. All these goodies work together, making Django a top choice for projects, whether they're a walk in the park or a brain-bending challenge.
|
||||
|
||||
##### Flask
|
||||
|
||||
On the other hand, Flask, a micro-framework, takes a minimalist approach, providing developers with the flexibility to choose components as needed. While Flask may be lighter than Django, it doesn't compromise on functionality. Its simplicity and modularity make it an excellent choice for small to medium-sized projects, allowing developers to tailor the framework to meet specific project requirements.
|
||||
|
||||
Both Django and Flask underscore Python's suitability for backend development, offering developers frameworks that cater to diverse project needs while maintaining Python's hallmark readability and efficiency.
|
||||
|
||||
#### Pros and Cons of Python
|
||||
|
||||
As with all other backend languages in this article, Python has some pros and cons you should consider before picking it as your first backend language.
|
||||
|
||||
##### Pros
|
||||
|
||||
- The syntax is very easy to learn because it’s very much like writing English.
|
||||
- The ecosystem is quite mature and has some nice frameworks that will contain all the tools you need to get started
|
||||
|
||||
##### Cons
|
||||
|
||||
- It’s not the most popular backend language, so while the frameworks available are constantly updated, they aren’t necessarily using the latest technology trends.
|
||||
- The GIL (Global Interpreter Lock) limits Python’s performance in multi-threaded applications.
|
||||
|
||||
### Java
|
||||
|
||||
Java has a massive presence and for good reason (according to [JetBrain’s survey in 2022, Java was used by 48% of developers](https://w3techs.com/technologies/details/pl-php)).It's the kind of programming language that's everywhere – serving up websites, running your favorite apps, and even powering big-scale enterprise systems.
|
||||
|
||||
#### Is it worth learning Java?
|
||||
|
||||
Now, learning Java, (a strongly typed, object oriented programming language (OOP), is a journey worth taking, but it's not a walk in the park. It's a bit like climbing a mountain – you start at the bottom with the basics, and as you ascend, you get into the nitty-gritty of things like object-oriented programming. The process will force you to learn a lot, which is a great thing, by the end you’ll have a lot of understanding of mechanics and concepts around OOP that can be extrapolated into other languages. However, that can also be overwhelming to some developers who just want to learn by building mini-projects. In those situations, the learning curve of Java might be too long (not steep, but long because there is a lot more to cover than with alternatives such as Python or JavaScript).
|
||||
|
||||
That said, the community is big and there are tons of resources, from online courses to forums, helping you navigate the Java landscape. And good reason, considering Java has been around for quite a while.
|
||||
|
||||
#### Use Cases and Robust Ecosystem
|
||||
|
||||
Java's everywhere. From web development to mobile apps, and even diving into the world of big data, Java's got its fingerprints all over. And if it’s not the language itself, it’s the Java Virtual Machine (JVM) powering some other language, like Spark.
|
||||
|
||||
Java’s the language of choice for many big enterprises given its innate robustness (the first version of the language was released in 1995, it’s had quite a long time to evolve), and its robust ecosystem of libraries and frameworks makes it a go-to for developers.
|
||||
|
||||
#### Pros and Cons of Java
|
||||
|
||||
For all its power and robustness, there are some negative (and positive) aspects to picking Java as your first backend language.
|
||||
|
||||
##### Pros
|
||||
|
||||
- Java has a mature ecosystem with a varied array of libraries and frameworks for you to try. The community has been working on them and evolving them for years in many cases, so they’re quite ready to develop enterprise-ready solutions.
|
||||
- Java’s multithreading support makes it ideal for some processing-heavy tasks in the backend of big applications.
|
||||
- Java’s heavy focus on object oriented programming makes it a great option for developers who enjoy that paradigm.
|
||||
|
||||
##### Cons
|
||||
|
||||
- Java’s verbose syntax might be a problem for some people. While you can still code without an issue, it all comes down to personal preference. If you like to write less and do more with your code, Java might not be the ideal pick for you. It’s verbosity can increase development time in some situations.
|
||||
- Java applications can have higher memory consumption than others, especially compared to others like PHP. While the reason for this is their entire architecture, the fact remains.
|
||||
|
||||
### JavaScript (Node.js)
|
||||
|
||||
With Node.js in the mix, JavaScript becomes a lingua franca in web development. In other words, you can use the same language both for the frontend (client side) and for the backend (server side) of your application.
|
||||
|
||||
That said, keep in mind that depending on the framework you’re using, while it might be JavaScript on both sides, the code and logic you use can be considerably different.
|
||||
|
||||
Remember that frontend code is often confused with framework code (as in React, Angular, Vue, etc) by some developers, simply because it’s all JavaScript. But don’t be confused, the backend lacks a lot of the extra “juice” added by the browser (like the DOM API and others).
|
||||
|
||||
#### Learning Advantages of Node.js
|
||||
|
||||
If you've got the basics of JavaScript down, even if your experience has only been on the frontend, diving into Node.js is like leveling up. It lets you use the same language for both frontend and backend, which means less time juggling languages and more time building cool stuff.
|
||||
|
||||
The event-driven, non-blocking architecture is one of the main features that make the language so special – it makes your web apps fast and efficient without you having to learn more complex concepts such as multi-threading. Plus, the community is constantly growing and there are tutorials everywhere to guide you through the Node.js universe.
|
||||
|
||||
If you were to rank languages based on the amount of content out there to learn them, JavaScript would be one of the first ones (if not the first one) on the list.
|
||||
|
||||
#### Key Frameworks and Development Tools
|
||||
|
||||
Now, let's talk about frameworks. In the case of JavaScript, this topic is so varied that recommending a single option for someone just getting started is really hard.
|
||||
|
||||
For example, if you want to go frontend agnostic, or in other words, you don’t care about the technology being used to develop the client side of your app, then a good starting option would be [Express.js](https://expressjs.com/). This framework used to be the industry standard. And while that’s no longer the case, it’s still a perfect first choice if you’re looking for something with the required functionality to make your life a lot easier.
|
||||
|
||||
Now, if on the other hand, you’re looking to build the frontend and the backend at the same time, then I would recommend going with [Next.js](https://nextjs.org/) if you’re already familiar with React. Or if on the other hand, you prefer Vue.js, then definitely try [Nuxt](https://nuxt.com/). Either one of those will help you get the job done with all the bells and whistles you can think of.
|
||||
|
||||
#### Does it make sense to pick up JavaScript as a backend language?
|
||||
|
||||
The answer to this question is always going to be “yes”, whether you’re coming from the frontend and you already have JS experience or if you’re picking it up from scratch. In fact, according to [StackOverflow’s 2023 survey, JavaScript is the most used language by professionals](https://survey.stackoverflow.co/2023/#most-popular-technologies-language-prof) (with 65.85% of the votes).
|
||||
|
||||

|
||||
|
||||
If you’re coming from the client side, then adopting JS for your backend will let you start working in minutes. You’ll probably spend more time learning the backend-specific concepts than the language itself.
|
||||
|
||||
On the other hand, if you’re coming from zero, or from other programming languages, JS has some quirks, for sure, but if you go the JS route, you’re already making way for a potential switch into the frontend in the future. Who knows, maybe in a few months you’ll also want to start working on the frontend, and by having picked up JS as your main backend language, you have 90% of the work already cut for you.
|
||||
|
||||
There is really no downside to picking JS as your first backend language.
|
||||
|
||||
#### Pros and Cons of JavaScript
|
||||
|
||||
While there might not be a downside to picking JS, there is no perfect language out there, so let’s take a look at some of the pros and cons before moving on to the next one.
|
||||
|
||||
##### Pros
|
||||
|
||||
- Going with JavaScript, you’re using the same language on the backend and on the frontend. There is less cognitive load while switching environments if you’re the one coding both sides of the app.
|
||||
- The ecosystem around JavaScript is one of the richest ones you can find. The community is constantly pushing the limits of the language and coming up with new solutions to everyday problems.
|
||||
- The simple syntax allows you to reduce development time because you don’t have to write as much code to achieve good results.
|
||||
|
||||
##### Cons
|
||||
|
||||
- Asynchronous programming can be hard for some developers coming from other languages, like Python for example.
|
||||
- The lack of strong types in JavaScript can cause some problems for big codebases.
|
||||
- The single-thread nature of the language makes it really hard to implement CPU-intensive tasks. While there is support for multi-threading, it’s not extensive nor commonly used.
|
||||
- Debugging asynchronous code can be difficult for new developers given the non-linear nature of it.
|
||||
|
||||
### PHP
|
||||
|
||||
Now, if you’re looking for something very well established in the web development industry, just like Java but with a shorter learning curve, then you’re probably looking for PHP.
|
||||
|
||||
> As a note about PHP’s relevancy, while many developers might claim that PHP is a dying tech, according to [W3Techs, over 75% of websites with a backend use PHP](https://w3techs.com/technologies/details/pl-php).
|
||||
|
||||
It's the glue that holds a ton of websites together, and its longevity in the web development scene is no accident.
|
||||
|
||||
#### Ease of Mastery and Vast Library Support
|
||||
|
||||
If you're diving into PHP, you wouldn’t be so wrong (no matter what others might tell you). It's got a gentle learning curve, which means you can start building things pretty quickly. Getting everything set up and working will probably take you 10 minutes, and you’ll be writing your first “hello world” 5 minutes after that.
|
||||
|
||||
The vast community support and an ocean of online resources make mastering PHP a breeze. Plus, its library support is like having a toolkit that's always expanding – you'll find what you need, whether you're wrangling databases, handling forms, or making your website dance with dynamic content.
|
||||
|
||||
If you’re looking to pick up PHP, look for the LAMP stack, which stands for **L**inux, **A**pache, **M**ySQL, and **P**HP. With that tech stack, you’ll have everything you need to start creating websites in no time.
|
||||
|
||||
#### Modern PHP Frameworks and Their Impact
|
||||
|
||||
If we’re talking about PHP frameworks, then we gotta talk about [Laravel](https://laravel.com/) and [Symfony](https://symfony.com/). They are like the rockstars of the modern PHP world.
|
||||
|
||||
Laravel comes with a lot of tools and features that help you speed up your development process. On the other side, Symfony has a modular architecture, making it a solid choice for projects of all sizes.
|
||||
|
||||
These frameworks showcase how PHP has evolved, staying relevant and powerful in the ever-changing landscape of web development.
|
||||
|
||||
#### Pros and Cons of PHP
|
||||
|
||||
Let’s take a look at some of the most common advantages of going with PHP for the backend and some cons to discuss why it might not be the best choice for you.
|
||||
|
||||
##### Pros
|
||||
|
||||
- PHP is designed for web development, which still makes it a very popular choice for a backend language.
|
||||
- PHP’s community is quite big, considering how old the language is, so if you need help, chances are, someone has the answer you’re looking for.
|
||||
|
||||
##### Cons
|
||||
|
||||
- One of the major complaints developers have about the language is its inconsistent function naming convention. While not a huge problem, it makes it very hard for developers to intuitively find the right function by name. This causes you to constantly verify your code against the documentation to make sure you’re not making mistakes.
|
||||
|
||||
### Go
|
||||
|
||||
Now, let's close in on Go, the programming language born at Google that's all about simplicity and efficiency. Go embraces a clean and straightforward syntax. Despite its simplicity, it focuses heavily on performance, making it an excellent choice for building modern, scalable applications.
|
||||
|
||||
According to the [PYPL index](https://pypl.github.io/PYPL.html) (using Google searches to weigh interest of developers in a particular language), we can see a clear worldwide growing interest in Go from the development community:
|
||||
|
||||

|
||||
|
||||
#### Concurrency and Scalability
|
||||
|
||||
Go stands out in the crowd, especially when it comes to handling concurrency and scalability. Its built-in support for concurrent programming, through goroutines and channels, makes it a standout choice for applications that need to juggle multiple tasks simultaneously. This makes Go particularly adept at handling the demands of today's highly concurrent and distributed systems. In other words, Go is a great choice for building microservices, a type of system that is very commonly used as the backend for complex web applications.
|
||||
|
||||
So yes, very relevant.
|
||||
|
||||
#### Learning Curve and Developer Productivity
|
||||
|
||||
Learning Go is a smooth ride, thanks to its simplicity and extensive documentation. Developers often find themselves quickly transitioning from understanding the basics to building robust applications.
|
||||
|
||||
The language's focus on developer productivity is evident in its quick compilation times and the absence of excessive boilerplate code, allowing developers to concentrate on building features rather than wrestling with the language itself.
|
||||
|
||||
#### Pros and Cons of Go
|
||||
|
||||
Let’s take a look at some pros and cons for the last programming language on our list.
|
||||
|
||||
##### Pros
|
||||
|
||||
- Go code compiles quickly, which in turn leads to very fast development cycles. This is a big plus if you’re developing a big application with a large codebase because other options might slow down your process with their compilation times.
|
||||
- Go's syntax is simple enough to make it easy to learn and understand for new developers.
|
||||
|
||||
##### Cons
|
||||
|
||||
- Go’s ecosystem is quite young when compared to the other alternatives here, so the maturity of the tools available might not be the same as, for example, Java or JavaScript tooling.
|
||||
|
||||
### Choosing the Ideal Backend Language
|
||||
|
||||
So, are these the best backend programming languages out there? Is there an absolute “best” backend programming language?
|
||||
|
||||
As you’ve probably seen by now, there is no “perfect” or “ideal” backend language. When it comes to picking one out of the huge number of alternatives, you have to consider other aspects outside of the language itself:
|
||||
|
||||
- What’s the size of your project? Are you building a large-scale platform? Or just a basic static website?
|
||||
- Do you mind spending more time learning or do you need to be efficient and start coding right away?
|
||||
- Do you already have some programming knowledge and would like to pick something that resembles what you already know? Or would you like to pick up something that’s entirely different?
|
||||
- Are you alone? Or are you part of a team?
|
||||
|
||||
Once you’ve answered those questions, you’ll probably have some idea of where to go, but then you should look into the language itself, specifically into:
|
||||
|
||||
- Does it have enough learning resources for you?
|
||||
- How big and active is the community around it?
|
||||
- Are the main frameworks still under development? Or have they been parked for a while?
|
||||
|
||||
In the end, you’re evaluating the language and its ecosystem, making sure they’re both evolving right along the web industry. If you find that there are aspects that are falling behind, then it probably isn’t a good choice.
|
||||
|
||||
A handy tool when trying to evaluate a language like that is [roadmap.sh](https://roadmap.sh).
|
||||
|
||||
[](https://roadmap.sh/backend)
|
||||
|
||||
<p align="center" style="font-size: 14px; margin-top: -10px; text-align: center">Small section of the full backend roadmap available on <a href="https://roadmap.sh/backend">roadmap.sh</a></p>
|
||||
|
||||
There you’ll find community-maintained roadmaps for many career paths within software development. In particular, for this article, the [backend roadmap](https://roadmap.sh/backend) is a great place to start, because while picking a backend language is important, you’ll see there that it’s not just about the language. In fact, there is a lot of tech around the language that is also required (I’m referring to databases, git, understanding how client-server communication works, and a big “etc).
|
||||
|
||||
### Jumpstarting Your Backend Development Journey
|
||||
|
||||
To get started with your backend development journey, it's crucial to have a roadmap that guides you through the learning process and equips you with the skills to build robust and scalable backend systems.
|
||||
|
||||
Lucky for you, if you’re reading this, that means you’ve found the most complete and comprehensive roadmap online: [roadmap.sh](https://roadmap.sh), the current [backend roadmap](https://roadmap.sh/backend) is filled with details of everything you should and could (optionally) learn in your journey to becoming a backend developer.
|
||||
|
||||
### Guided Learning: From Online Courses to Bootcamps
|
||||
|
||||
Online courses and bootcamps serve as invaluable companions on your learning expedition. Platforms like Udemy, Coursera, and freeCodeCamp offer comprehensive backend development courses.
|
||||
|
||||
These resources not only cover programming languages like Python, Java, or JavaScript but also dive deep into frameworks like Django, Express.js, or Laravel. For those seeking a more immersive experience, coding bootcamps provide intensive, hands-on training to fast-track your backend development skills.
|
||||
|
||||
Whatever choice you go for, make sure you’re not following trends or just copying the learning methods of others. Learning is a very personal experience and what works for others might not work for you, and vice versa. So make sure to do the proper research and figure out what option works best for you.
|
||||
|
||||
### Building Community Connections for Learning Support
|
||||
|
||||
Joining developer communities (there are several on Twitter for example), forums like Stack Overflow, or participating in social media groups dedicated to backend development creates a network of support.
|
||||
|
||||
Engaging with experienced developers, sharing challenges, and seeking advice fosters a collaborative learning environment. Attend local meetups or virtual events if you can to connect with professionals in the field, gaining insights and building relationships that can prove invaluable throughout your journey.
|
||||
|
||||
### Think about you and your project
|
||||
|
||||
There are many ways to go about picking the ideal backend language for you. If there is anything you should take home with you after reading this article, it is that most languages are equivalent in the sense that you’ll be able to do pretty much everything with any of them.
|
||||
|
||||
So what criteria can you use to pick the “right one” for you?
|
||||
|
||||
The questions you should also be asking yourself are:
|
||||
|
||||
- What’s your preference for a language? Do you like Object Oriented Programming (OOP) or are you more of a functional programming type of dev? Do you like statically typed programming languages or loosely typed ones? Personal preferences should also play an important role at the time of picking your ideal programming language.
|
||||
- What does my project need? After all, project requirements sometimes dictate technology. Keep that in mind, check if the project’s needs and your personal preferences align, and try to weigh in pros and cons if they don’t.
|
||||
|
||||
In the end, personal preference and actual project requirements (if you have any) are very important, because both will influence how much you enjoy (or don’t enjoy) the learning process.
|
||||
|
||||
### Crafting a Portfolio to Display Your Backend Skills:
|
||||
|
||||
As you accumulate skills and knowledge, showcase your journey through a well-crafted portfolio. Include projects that highlight your backend skills, demonstrating your ability to - design databases, implement server-side logic, and integrate with client side technologies. Whether it's a dynamic web application, a RESTful API, or a data-driven project, your portfolio becomes a tangible representation of your backend development capabilities for potential employers or collaborators.
|
||||
|
||||
When it comes to deciding where to publish this portfolio, you have some options, such as directly on your GitHub profile (if you have one), or perhaps on your own personal website where you can share some design thoughts about each project along with the code.
|
||||
|
||||
In the end, the important thing is that you should be sharing your experience somewhere, especially when you don’t have working experience in the field.
|
||||
|
||||
### Conclusion
|
||||
|
||||
In the end, there are many backend programming languages to choose from, and what language you go for, is up to you and your particular context/needs. All I can do is guide you to the door, but you have to cross it yourself. Some interesting options are:
|
||||
|
||||
- Python with its English-like syntax.
|
||||
- Java with its formal syntax and enterprise support.
|
||||
- JavaScript with its flexibility and ability to jump between frontend and backend.
|
||||
- PHP with its proven record of success.
|
||||
- And Go, with its performance and scalability focus.
|
||||
|
||||
You’re the one who gets to decide, but just know that no matter what you choose, getting started in backend development is a one-way street. You’ll be learning from this moment on, and you’ll be jumping from one language to the other as the field evolves.
|
||||
|
||||
Remember that there is a very detailed version of a [backend roadmap here](https://roadmap.sh/backend), it might be a great place to get started! And if you’re also interested in frontend development, there is an [equally handy roadmap](https://roadmap.sh/frontend) here as well!
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -49,7 +49,7 @@ On a high level, LLMs can be categorized into two types i.e. Base LLMs and Instr
|
||||
|
||||
### Base LLMs
|
||||
|
||||
Base LLMs are the LLMs which are designed to predict the next word based on the training data. They are not designed to answer questions, carry out conversations or help solve problems. For example, if you give a base LLM the sentence "In this book about LLMs, we will discuss", it might complete this sentence and give you "In this book about LLMs, we will discsus **what LLMs are, how they work, and how you can leverage them in your applications.**." Or if you give it "What are some famous social networks?", instead of answering it might give back "Why do people use social networks?" or "What are some of the benefits of social networks?". As you can see, it is giving us relevant text but it is not answering the question. This is where the Instruction tuned LLMs come in to the picture.
|
||||
Base LLMs are the LLMs which are designed to predict the next word based on the training data. They are not designed to answer questions, carry out conversations or help solve problems. For example, if you give a base LLM the sentence "In this book about LLMs, we will discuss", it might complete this sentence and give you "In this book about LLMs, we will discuss **what LLMs are, how they work, and how you can leverage them in your applications.**." Or if you give it "What are some famous social networks?", instead of answering it might give back "Why do people use social networks?" or "What are some of the benefits of social networks?". As you can see, it is giving us relevant text but it is not answering the question. This is where the Instruction tuned LLMs come in to the picture.
|
||||
|
||||
### Instruction tuned LLMs
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
The Head and Stack in JavaScript Engine are two different data structures that store data in different ways.
|
||||
The Heap and Stack in JavaScript Engine are two different data structures that store data in different ways.
|
||||
|
||||
## Stack
|
||||
|
||||
|
||||
17
src/data/question-groups/nodejs/content/commonjs-vs-esm.md
Normal file
17
src/data/question-groups/nodejs/content/commonjs-vs-esm.md
Normal file
@@ -0,0 +1,17 @@
|
||||
CommonJS and ES Modules are two different module systems in JavaScript. CommonJS is the module system used in Node.js, while ES Modules are the module system used in browsers and TypeScript.
|
||||
|
||||
## CommonJS
|
||||
|
||||
```js
|
||||
const fs = require('fs');
|
||||
```
|
||||
|
||||
CommonJS modules are loaded synchronously. This means that the module is loaded and evaluated before the code using the module is executed. It uses `require()` to load modules and `module.exports` to export modules.
|
||||
|
||||
## ES Modules
|
||||
|
||||
```js
|
||||
import fs from 'fs';
|
||||
```
|
||||
|
||||
ES Modules are loaded asynchronously. This means that the module is loaded and evaluated when the module is used. It uses `import` to load modules and `export` to export modules.
|
||||
66
src/data/question-groups/nodejs/content/error-handling.md
Normal file
66
src/data/question-groups/nodejs/content/error-handling.md
Normal file
@@ -0,0 +1,66 @@
|
||||
There are four fundamental strategies to report errors in Node.js:
|
||||
|
||||
## `try...catch` blocks
|
||||
|
||||
`try...catch` blocks are the most basic way to handle errors in JavaScript. They are synchronous and can only be used to handle errors in synchronous code. They are not suitable for asynchronous code, such as callbacks and promises.
|
||||
|
||||
```js
|
||||
import fs from 'node:fs';
|
||||
|
||||
try {
|
||||
const data = fs.readFileSync('file.md', 'utf-8');
|
||||
console.log(data);
|
||||
} catch (err) {
|
||||
console.error(err);
|
||||
}
|
||||
```
|
||||
|
||||
## Callbacks
|
||||
|
||||
Callbacks are the most common way to handle errors in asynchronous code. They are passed as the last argument to a function and are called when the function completes or fails.
|
||||
|
||||
```js
|
||||
import fs from 'node:fs';
|
||||
|
||||
fs.readFile('file.md', 'utf-8', (err, data) => {
|
||||
if (err) {
|
||||
console.error(err);
|
||||
return;
|
||||
}
|
||||
|
||||
console.log(data);
|
||||
});
|
||||
```
|
||||
|
||||
## Promises
|
||||
|
||||
Promises are a more modern way to handle errors in asynchronous code. They are returned by functions and can be chained together. They are resolved when the function completes and rejected when it fails.
|
||||
|
||||
```js
|
||||
import fs from 'node:fs/promises';
|
||||
|
||||
fs.readFile('file.md', 'utf-8')
|
||||
.then((data) => {
|
||||
console.log(data);
|
||||
})
|
||||
.catch((err) => {
|
||||
console.error(err);
|
||||
});
|
||||
```
|
||||
|
||||
## Event emitters
|
||||
|
||||
Event emitters are a more advanced way to handle errors in asynchronous code. They are returned by functions and emit an `error` event when they fail. They are resolved when the function completes and rejected when it fails.
|
||||
|
||||
```js
|
||||
import fs from 'node:fs';
|
||||
|
||||
const reader = fs.createReadStream('file.md', 'utf-8');
|
||||
reader.on('data', (data) => {
|
||||
console.log(data);
|
||||
});
|
||||
|
||||
reader.on('error', (err) => {
|
||||
console.error(err);
|
||||
});
|
||||
```
|
||||
18
src/data/question-groups/nodejs/content/exit-codes.md
Normal file
18
src/data/question-groups/nodejs/content/exit-codes.md
Normal file
@@ -0,0 +1,18 @@
|
||||
The following exit codes are used in Node.js:
|
||||
|
||||
- `0`: Success
|
||||
- `1`: Uncaught Fatal Exception
|
||||
- `2`: Unused
|
||||
- `3`: Internal JavaScript Parse Error
|
||||
- `4`: Internal JavaScript Evaluation Failure
|
||||
- `5`: Fatal Error
|
||||
- `6`: Non-function Internal Exception Handler
|
||||
- `7`: Internal Exception Handler Run-Time Failure
|
||||
- `8`: Unused
|
||||
- `9`: Invalid Argument
|
||||
- `10`: Internal JavaScript Run-Time Failure
|
||||
- `12`: Invalid Debug Argument
|
||||
- `13`: Uncaught Exception
|
||||
- `14`: Unhandled Promise Rejection
|
||||
- `15`: Fatal Exception
|
||||
- `16`: Signal Exits
|
||||
@@ -0,0 +1,18 @@
|
||||
In order to take user input from the command line, you can use the `readline` module. It provides an interface for reading data from a Readable stream (such as `process.stdin`) one line at a time.
|
||||
|
||||
```js
|
||||
import readline from 'node:readline';
|
||||
import { stdin as input, stdout as output } from 'node:process';
|
||||
|
||||
const rl = readline.createInterface({ input, output });
|
||||
|
||||
rl.question('What do you think of Node.js? ', (answer) => {
|
||||
console.log(`Thank you for your valuable feedback: ${answer}`);
|
||||
rl.close();
|
||||
});
|
||||
|
||||
rl.on('close', () => {
|
||||
console.log('\nBYE BYE !!!');
|
||||
process.exit(0);
|
||||
});
|
||||
```
|
||||
25
src/data/question-groups/nodejs/content/order-priority.md
Normal file
25
src/data/question-groups/nodejs/content/order-priority.md
Normal file
@@ -0,0 +1,25 @@
|
||||
Order priorities of `process.nextTick`, `Promise`, `setTimeout` and `setImmediate` are as follows:
|
||||
|
||||
1. `process.nextTick`: Highest priority, executed immediately after the current event loop cycle, before any other I/O events or timers.
|
||||
2. `Promise`: Executed in the microtask queue, after the current event loop cycle, but before the next one.
|
||||
3. `setTimeout`: Executed in the timer queue, after the current event loop cycle, with a minimum delay specified in milliseconds.
|
||||
4. `setImmediate`: Executed in the check queue, but its order may vary based on the system and load. It generally runs in the next iteration of the event loop after I/O events.
|
||||
|
||||
```js
|
||||
console.log('start');
|
||||
Promise.resolve().then(() => console.log('Promise'));
|
||||
setTimeout(() => console.log('setTimeout'), 0);
|
||||
process.nextTick(() => console.log('process.nextTick'));
|
||||
setImmediate(() => console.log('setImmediate'));
|
||||
console.log('end');
|
||||
|
||||
// Output:
|
||||
// start
|
||||
// end
|
||||
// process.nextTick
|
||||
// Promise
|
||||
// setTimeout
|
||||
// setImmediate
|
||||
```
|
||||
|
||||
In summary, the order of execution is generally `process.nextTick` > `Promise` > `setTimeout` > `setImmediate`. However, keep in mind that the behavior may vary in specific situations, and the order might be influenced by factors such as system load and other concurrent operations.
|
||||
15
src/data/question-groups/nodejs/content/process-argv.md
Normal file
15
src/data/question-groups/nodejs/content/process-argv.md
Normal file
@@ -0,0 +1,15 @@
|
||||
`process.argv` is an array containing the command-line arguments passed when the Node.js process was launched. The first element is the path to the Node.js executable, the second element is the path to the JavaScript file being executed, and the remaining elements are the command-line arguments.
|
||||
|
||||
```js
|
||||
node index.js hello world
|
||||
```
|
||||
|
||||
```js
|
||||
console.log(process.argv);
|
||||
// [
|
||||
// '/usr/local/bin/node', -> path to the Node.js executable
|
||||
// '/Users/username/projects/nodejs/index.js', -> path to the JavaScript file being executed
|
||||
// 'hello', -> command-line argument
|
||||
// 'world' -> command-line argument
|
||||
// ]
|
||||
```
|
||||
@@ -0,0 +1,9 @@
|
||||
`process.cwd()` returns the current working directory of the Node.js process, while `__dirname` returns the directory name of the current module.
|
||||
|
||||
```js
|
||||
console.log(process.cwd());
|
||||
// /Users/username/projects/nodejs
|
||||
|
||||
console.log(__dirname);
|
||||
// /Users/username/projects/nodejs/src
|
||||
```
|
||||
14
src/data/question-groups/nodejs/content/web-server.md
Normal file
14
src/data/question-groups/nodejs/content/web-server.md
Normal file
@@ -0,0 +1,14 @@
|
||||
To create a minimal `Hello, World!` HTTP server in Node.js, you can use the `http` module. It provides an HTTP server, and the createServer() method sets up a server instance with a callback function to handle incoming requests
|
||||
|
||||
```js
|
||||
import http from 'node:http';
|
||||
|
||||
const server = http.createServer((req, res) => {
|
||||
res.writeHead(200, { 'Content-Type': 'text/plain' });
|
||||
res.end('Hello World\n');
|
||||
});
|
||||
|
||||
server.listen(3000, () => {
|
||||
console.log('Server running at http://localhost:3000/');
|
||||
});
|
||||
```
|
||||
227
src/data/question-groups/nodejs/nodejs.md
Normal file
227
src/data/question-groups/nodejs/nodejs.md
Normal file
@@ -0,0 +1,227 @@
|
||||
---
|
||||
order: 1
|
||||
briefTitle: 'Node.js'
|
||||
briefDescription: 'Test, rate and improve your Node.js knowledge with these questions.'
|
||||
title: 'Node.js Questions'
|
||||
description: 'Curated list of Node.js questions to test, rate and improve your knowledge. Questions are based on real world experience and knowledge.'
|
||||
isNew: true
|
||||
seo:
|
||||
title: 'Node.js Questions'
|
||||
description: 'Curated list of Node.js questions to test, rate and improve your knowledge. Questions are based on real world experience and knowledge.'
|
||||
keywords:
|
||||
- 'node.js quiz'
|
||||
- 'node.js questions'
|
||||
- 'node.js interview questions'
|
||||
- 'node.js interview'
|
||||
- 'node.js test'
|
||||
sitemap:
|
||||
priority: 1
|
||||
changefreq: 'monthly'
|
||||
questions:
|
||||
- question: What is Node.js?
|
||||
answer: Node.js is an open-source and cross-platform JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is REPL in Node.js?
|
||||
answer: |
|
||||
REPL stands for Read-Eval-Print-Loop. It is an interactive shell that allows you to execute JavaScript code and view the output immediately. It is useful for testing small snippets of code and experimenting with the Node.js API.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is the difference between Node.js and JavaScript?
|
||||
answer: Node.js is a runtime environment for JavaScript. JavaScript is a programming language used to create web applications. Node.js is a runtime environment that can execute JavaScript code outside of a web browser.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is Event Loop in Node.js?
|
||||
answer: |
|
||||
The event loop is a single-threaded loop responsible for handling all asynchronous callbacks in Node.js. It continuously checks for events and executes associated callback functions, allowing Node.js to handle asynchronous tasks efficiently. Its non-blocking I/O model ensures that it can process multiple operations simultaneously without waiting for one to complete before moving on to the next, contributing to its scalability and performance.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is the difference between Node.js and AJAX?
|
||||
answer: |
|
||||
Node.js is a server-side runtime for JavaScript, while AJAX is a client-side technique for asynchronous communication with the server.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What are modules in Node.js?
|
||||
answer: |
|
||||
Modules are reusable blocks of code that can be imported into other files. They are used to encapsulate related code into a single unit of code that can be used in other parts of the program. It allow us to split our code into multiple files and reuse it across multiple files. Some built-in modules include `fs`, `http`, `path`, `url`, `util`, etc.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: Difference between CommonJS and ESM?
|
||||
answer: commonjs-vs-esm.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is the `global` object in Node.js?
|
||||
answer: |
|
||||
The `global` object is a global namespace object that contains all global variables, functions, and objects. It is similar to the `window` object in the browser. It can be accessed from anywhere in the program without importing it.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is the difference between `process.nextTick()` and `setImmediate()`?
|
||||
answer: |
|
||||
`process.nextTick()` and `setImmediate()` are both used to schedule a callback function to be executed in the next iteration of the event loop. The difference is that `process.nextTick()` executes the callback at the end of the current iteration of the event loop, while `setImmediate()` executes the callback at the beginning of the next iteration of the event loop.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is `setInterval()`?
|
||||
answer: |
|
||||
`setInterval()` is a global function that helps you execute a function repeatedly at a fixed delay. It returns an interval ID that uniquely identifies the interval, which can be used to cancel the interval using the `clearInterval()` function.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is `setTimeout()`?
|
||||
answer: |
|
||||
`setTimeout()` is a global function that helps you execute a function after a specified delay. It returns a timeout ID that uniquely identifies the timeout, which can be used to cancel the timeout using the `clearTimeout()` function.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What are Event Emitters in Node.js?
|
||||
answer: |
|
||||
Event Emitters is a class that can be used to emit named events and register listeners for those events. It is used to handle asynchronous events in Node.js.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is `npm`?
|
||||
answer: |
|
||||
`npm` is a package manager for Node.js. It is used to install, update, and remove packages from the Node.js ecosystem. It is also used to manage dependencies for Node.js projects.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is the full form of `npm`?
|
||||
answer: |
|
||||
`npm` stands for Node Package Manager.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is `npx`?
|
||||
answer: |
|
||||
`npx` is a tool that allows you to run Node.js packages without installing them. It is used to execute Node.js packages that are not installed globally.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is `process.cwd()`?
|
||||
answer: |
|
||||
`process.cwd()` returns the current working directory of the Node.js process. It is similar to `pwd` in Unix.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is the difference between `process.cwd()` and `__dirname`?
|
||||
answer: process-cwd-vs-dirname.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is `__filename`?
|
||||
answer: |
|
||||
`__filename` is a global variable that contains the absolute path of the current file.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is `process.argv`?
|
||||
answer: process-argv.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is the purpose of `fs` module?
|
||||
answer: |
|
||||
The File System (fs) module is used to perform file operations such as reading, writing, and deleting files. All file system operations have synchronous and asynchronous forms.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What is the purpose of `path` module?
|
||||
answer: |
|
||||
The Path module is used to perform operations on file and directory paths. It provides methods for resolving and normalizing paths, joining paths, and extracting file and directory names.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: How to read a file in Node.js?
|
||||
answer: |
|
||||
The `fs.readFile()` method is used to read the contents of a file asynchronously. It takes the path of the file to be read and a callback function as arguments. The callback function is called with two arguments, `err` and `data`. If an error occurs while reading the file, the `err` argument will contain the error object. Otherwise, the `data` argument will contain the contents of the file.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: How to load environment variables from a `.env` file in Node.js?
|
||||
answer: |
|
||||
The `dotenv` package is used to load environment variables from a `.env` file into `process.env`. It is used to store sensitive information such as API keys, database credentials, etc. in a `.env` file instead of hardcoding them in the source code.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: How to access environment variables in Node.js?
|
||||
answer: |
|
||||
Environment variables can be accessed using the `process.env` object. It is an object that contains all the environment variables defined in the current process.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: How to take user input from the command line in Node.js?
|
||||
answer: input-from-command-line.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: How to create a web server in Node.js?
|
||||
answer: web-server.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: What are streams in Node.js?
|
||||
answer: |
|
||||
Streams are objects that allow you to read data from a source or write data to a destination in a continuous manner. They are used to handle large amounts of data efficiently.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is difference between `fork` and `spawn` methods of `child_process` module?
|
||||
answer: |
|
||||
The `fork` method is used when you want to run another JavaScript file in a separate worker. It's like having a friend with a specific task. You can communicate with them via messages and they can send messages back to you. The `spawn` method is used when you want to run a command in a separate process. It's like asking someone to do a specific. You can communicate with them via stdin/stdout/stderr, but it's more like giving orders and getting results.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is the `os` module?
|
||||
answer: |
|
||||
The `os` module provides methods for interacting with the operating system. It can be used to get information about the operating system, such as the hostname, platform, architecture, etc.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Beginner'
|
||||
- question: Can you access the DOM in Node.js?
|
||||
answer: |
|
||||
No, you cannot access the DOM in Node.js because it does not have a DOM. It is a server-side runtime for JavaScript, so it does not have access to the browser's DOM.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is Clustering in Node.js?
|
||||
answer: |
|
||||
Clustering is a technique used to distribute the load across multiple processes. It is used to improve the performance and scalability of Node.js applications.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: Why memory leak happens in Node.js?
|
||||
answer: |
|
||||
Memory leaks happen when a program allocates memory but does not release it when it is no longer needed. This can happen due to bugs in the program or due to the way the program is designed. In Node.js, memory leaks can happen due to the use of closures, circular references, and global variables.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is the order priority of `process.nextTick`, `Promise`, `setTimeout`, and `setImmediate`?
|
||||
answer: order-priority.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: What is `process.exit()`?
|
||||
answer: |
|
||||
`process.exit()` is a method that can be used to exit the current process. It takes an optional exit code as an argument. If no exit code is specified, it defaults to 0.
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: Different exit codes in Node.js?
|
||||
answer: exit-codes.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
- question: How Node.js handle errors?
|
||||
answer: error-handling.md
|
||||
topics:
|
||||
- 'Core'
|
||||
- 'Intermediate'
|
||||
---
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/ai-data-scientist.json'
|
||||
pdfUrl: '/pdfs/roadmaps/ai-data-scientist.pdf'
|
||||
order: 6
|
||||
briefTitle: 'AI and Data Scientist'
|
||||
briefDescription: 'Step by step guide to becoming an AI and Data Scientist in 2023'
|
||||
briefDescription: 'Step by step guide to becoming an AI and Data Scientist in 2024'
|
||||
title: 'AI and Data Scientist Roadmap'
|
||||
description: 'Step by step guide to becoming an AI and Data Scientist in 2023'
|
||||
description: 'Step by step guide to becoming an AI and Data Scientist in 2024'
|
||||
hasTopics: true
|
||||
isNew: true
|
||||
dimensions:
|
||||
@@ -21,8 +21,8 @@ seo:
|
||||
title: 'AI and Data Scientist Roadmap'
|
||||
description: 'Learn to become an AI and Data Scientist using this roadmap. Community driven, articles, resources, guides, interview questions, quizzes for modern backend development.'
|
||||
keywords:
|
||||
- 'ai and data scientist roadmap 2023'
|
||||
- 'ai and data scientist roadmap 2023'
|
||||
- 'ai and data scientist roadmap 2024'
|
||||
- 'ai and data scientist roadmap 2024'
|
||||
- 'guide to becoming an ai and data scientist'
|
||||
- 'ai and data scientist roadmap'
|
||||
- 'ai scientist'
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
pdfUrl: '/pdfs/roadmaps/android.pdf'
|
||||
order: 4
|
||||
briefTitle: 'Android'
|
||||
briefDescription: 'Step by step guide to becoming an Android Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming an Android Developer in 2024'
|
||||
title: 'Android Developer'
|
||||
description: 'Step by step guide to becoming an Android developer in 2023'
|
||||
description: 'Step by step guide to becoming an Android developer in 2024'
|
||||
hasTopics: true
|
||||
isNew: true
|
||||
dimensions:
|
||||
@@ -12,7 +12,7 @@ dimensions:
|
||||
height: 2197.76
|
||||
schema:
|
||||
headline: 'Android Developer Roadmap'
|
||||
description: 'Learn how to become a Android Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Android Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/android.png'
|
||||
datePublished: '2023-01-24'
|
||||
dateModified: '2023-10-24'
|
||||
|
||||
@@ -3,16 +3,16 @@ jsonUrl: '/jsons/roadmaps/angular.json'
|
||||
pdfUrl: '/pdfs/roadmaps/angular.pdf'
|
||||
order: 3
|
||||
briefTitle: 'Angular'
|
||||
briefDescription: 'Step by step guide to become a Angular Developer in 2023'
|
||||
briefDescription: 'Step by step guide to become a Angular Developer in 2024'
|
||||
title: 'Angular Developer'
|
||||
description: 'Everything that is there to learn about Angular and the ecosystem in 2023.'
|
||||
description: 'Everything that is there to learn about Angular and the ecosystem in 2024.'
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
width: 968
|
||||
height: 2277.8
|
||||
schema:
|
||||
headline: 'Angular Developer Roadmap'
|
||||
description: 'Learn how to become a Angular Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Angular Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/angular.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -9,4 +9,4 @@ Type guards are typically used for narrowing a type and are pretty similar to fe
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Types Guards - Blog](https://blog.logrocket.com/how-to-use-type-guards-typescript/)
|
||||
- [TypeScript Type Guards Explained](https://www.youtube.com/watch?v=feeeitmtdwg)
|
||||
- [TypeScript Type Guards Explained](https://www.youtube.com/watch?v=FEeEItMtDwg)
|
||||
@@ -4,6 +4,5 @@ Marble testing allows you to test asynchronous RxJS code synchronously and step-
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Angular Marble Testing: A Brief Introduction](https://www.altamira.ai/blog/angular-marble-testing-a-brief-introduction/)
|
||||
- [IUnderstanding Marble Diagrams for Reactive Streams](https://medium.com/@jshvarts/read-marble-diagrams-like-a-pro-3d72934d3ef5)
|
||||
- [Understanding Marble Diagrams for Reactive Streams](https://medium.com/@jshvarts/read-marble-diagrams-like-a-pro-3d72934d3ef5)
|
||||
- [Interactive Diagrams](https://rxmarbles.com/#from)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/aspnet-core.json'
|
||||
pdfUrl: '/pdfs/roadmaps/aspnet-core.pdf'
|
||||
order: 9
|
||||
briefTitle: 'ASP.NET Core'
|
||||
briefDescription: 'Step by step guide to becoming an ASP.NET Core Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming an ASP.NET Core Developer in 2024'
|
||||
title: 'ASP.NET Core Developer'
|
||||
description: 'Step by step guide to becoming an ASP.NET core developer in 2023'
|
||||
description: 'Step by step guide to becoming an ASP.NET core developer in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2773.45
|
||||
schema:
|
||||
headline: 'ASP.NET Core Developer Roadmap'
|
||||
description: 'Learn how to become a ASP.NET Core Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a ASP.NET Core Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/aspnet-core.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/aws.json'
|
||||
pdfUrl: '/pdfs/roadmaps/aws.pdf'
|
||||
order: 14
|
||||
briefTitle: 'AWS'
|
||||
briefDescription: 'Step by step guide to learning AWS in 2023'
|
||||
briefDescription: 'Step by step guide to learning AWS in 2024'
|
||||
title: 'AWS Roadmap'
|
||||
description: 'Step by step guide to learning AWS in 2023'
|
||||
description: 'Step by step guide to learning AWS in 2024'
|
||||
isNew: true
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,20 +13,20 @@ dimensions:
|
||||
height: 2183.87
|
||||
schema:
|
||||
headline: 'AWS Roadmap'
|
||||
description: 'Learn how to use AWS with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to use AWS with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/aws.png'
|
||||
datePublished: '2023-11-29'
|
||||
dateModified: '2023-11-29'
|
||||
seo:
|
||||
title: 'AWS Roadmap - roadmap.sh'
|
||||
description: 'Step by step guide to learn AWS in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Step by step guide to learn AWS in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
keywords:
|
||||
- 'aws tutorial'
|
||||
- 'step by step guide for aws'
|
||||
- 'aws for beginners'
|
||||
- 'how to learn aws'
|
||||
- 'use aws in production'
|
||||
- 'aws roadmap 2023'
|
||||
- 'aws roadmap 2024'
|
||||
- 'guide to learning aws'
|
||||
- 'aws roadmap'
|
||||
- 'aws learning path'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/backend.json'
|
||||
pdfUrl: '/pdfs/roadmaps/backend.pdf'
|
||||
order: 2
|
||||
briefTitle: 'Backend'
|
||||
briefDescription: 'Step by step guide to becoming a backend developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a backend developer in 2024'
|
||||
title: 'Backend Developer'
|
||||
description: 'Step by step guide to becoming a modern backend developer in 2023'
|
||||
description: 'Step by step guide to becoming a modern backend developer in 2024'
|
||||
hasTopics: true
|
||||
isForkable: true
|
||||
tnsBannerLink: 'https://thenewstack.io?utm_source=roadmap.sh&utm_medium=Referral&utm_campaign=Alert'
|
||||
@@ -29,8 +29,8 @@ seo:
|
||||
title: 'Backend Developer Roadmap: What is Backend Development?'
|
||||
description: 'Learn what backend development is, what backend developers do and how to become one using our community-driven roadmap.'
|
||||
keywords:
|
||||
- 'backend roadmap 2023'
|
||||
- 'backend developer roadmap 2023'
|
||||
- 'backend roadmap 2024'
|
||||
- 'backend developer roadmap 2024'
|
||||
- 'guide to becoming a developer'
|
||||
- 'guide to becoming a backend developer'
|
||||
- 'backend roadmap'
|
||||
|
||||
@@ -10,4 +10,4 @@ Visit the following resources to learn more:
|
||||
- [Codeacademy - Free Course](https://www.codecademy.com/learn/learn-java)
|
||||
- [W3 Schools Tutorials](https://www.w3schools.com/java/)
|
||||
- [Java Crash Course](https://www.youtube.com/watch?v=eIrMbAQSU34)
|
||||
- [Complete Java course](https://www.youtube.com/watch?v=xk4_1vdrzzo)
|
||||
- [Complete Java course](https://www.youtube.com/watch?v=xk4_1vDrzzo)
|
||||
@@ -10,7 +10,7 @@ Visit the following resources to learn more:
|
||||
|
||||
- [What is HTTPS?](https://www.cloudflare.com/en-gb/learning/ssl/what-is-https/)
|
||||
- [Why HTTPS Matters](https://developers.google.com/web/fundamentals/security/encrypt-in-transit/why-https)
|
||||
- [Enabling HTTPS on Your Servers](https://developers.google.com/web/fundamentals/security/encrypt-in-transit/enable-https)
|
||||
- [Enabling HTTPS on Your Servers](https://web.dev/articles/enable-https)
|
||||
- [How HTTPS works (comic)](https://howhttps.works/)
|
||||
- [SSL, TLS, HTTP, HTTPS Explained](https://www.youtube.com/watch?v=hExRDVZHhig)
|
||||
- [HTTPS — Stories from the field](https://www.youtube.com/watch?v=GoXgl9r0Kjk)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/blockchain.json'
|
||||
pdfUrl: '/pdfs/roadmaps/blockchain.pdf'
|
||||
order: 6
|
||||
briefTitle: 'Blockchain'
|
||||
briefDescription: 'Step by step guide to becoming a blockchain developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a blockchain developer in 2024'
|
||||
title: 'Blockchain Developer'
|
||||
description: 'Step by step guide to becoming a blockchain developer in 2023.'
|
||||
description: 'Step by step guide to becoming a blockchain developer in 2024.'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2173.87
|
||||
schema:
|
||||
headline: 'Blockchain Developer Roadmap'
|
||||
description: 'Learn how to become a Blockchain Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Blockchain Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/blockchain.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
@@ -21,11 +21,11 @@ seo:
|
||||
title: 'Blockchain Developer Roadmap: Learn to become a blockchain developer'
|
||||
description: 'Learn to become a blockchain developer using this roadmap. Community driven, articles, resources, guides, interview questions, quizzes for modern backend development.'
|
||||
keywords:
|
||||
- 'blockchain roadmap 2023'
|
||||
- 'blockchain roadmap 2024'
|
||||
- 'web3 developer roadmap'
|
||||
- 'web3 developer roadmap 2023'
|
||||
- 'web3 developer roadmap 2024'
|
||||
- 'web3 roadmap'
|
||||
- 'blockchain developer roadmap 2023'
|
||||
- 'blockchain developer roadmap 2024'
|
||||
- 'guide to becoming a blockchain developer'
|
||||
- 'guide to becoming a blockchain developer'
|
||||
- 'blockchain roadmap'
|
||||
|
||||
@@ -6,7 +6,7 @@ This decentralization enables use-cases that were previously impossible, such as
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Why Blockchain?](https://www.blockchain.education/blockchain101/blockchain)
|
||||
- [Why Blockchain?](https://chain.link/education-hub/blockchain)
|
||||
- [What Is The Blockchain And Why Does It Matter?](https://www.forbes.com/sites/theyec/2020/05/18/what-is-the-blockchain-and-why-does-it-matter/)
|
||||
- [Web3/Crypto: Why Bother?](https://continuations.com/post/671863718643105792/web3crypto-why-bother)
|
||||
- [Why is Blockchain Important and Why Does it Matter](https://www.simplilearn.com/tutorials/blockchain-tutorial/why-is-blockchain-important)
|
||||
|
||||
@@ -4,7 +4,7 @@ A blockchain is a decentralized, distributed, and oftentimes public, digital led
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Introduction to Blockchain](https://www.blockchain.education/blockchain101/blockchain)
|
||||
- [Introduction to Blockchain](https://chain.link/education-hub/blockchain)
|
||||
- [Blockchain Explained](https://www.investopedia.com/terms/b/blockchain.asp)
|
||||
- [How does a blockchain work?](https://youtu.be/SSo_EIwHSd4)
|
||||
- [What Is a Blockchain? | Blockchain Basics for Developers](https://youtu.be/4ff9esY_4aU)
|
||||
|
||||
@@ -8,4 +8,4 @@ Visit the following resources to learn more:
|
||||
|
||||
- [Layer-1 and Layer-2 Blockchain Scaling Solutions](https://www.gemini.com/cryptopedia/blockchain-layer-2-network-layer-1-network)
|
||||
- [Layer 2 - Binance Academy](https://academy.binance.com/en/glossary/layer-2)
|
||||
- [Develop a ZK-powered Layer 2 with the Polgyon CDK open-source framework](https://wiki.polygon.technology/docs/cdk/)
|
||||
- [Develop a ZK-powered Layer 2 with the Polygon CDK open-source framework](https://wiki.polygon.technology/docs/cdk/)
|
||||
@@ -1,6 +1,6 @@
|
||||
# Blockchain Oracles
|
||||
|
||||
A blockchain oracle is a third-party service that connects smart contracts with the outside world, primarily to feed information in from the world, but also the reverse. Information from the world encapsulates multiple sources so that decentralised knowledge is obtained.
|
||||
A blockchain oracle is a third-party service that connects smart contracts with the outside world, primarily to feed information in from the world, but also the reverse. Information from the world encapsulates multiple sources so that decentralized knowledge is obtained.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -4,6 +4,6 @@ A smart contract is a computer program or a transaction protocol that is intende
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Smart Contracts Introduction](https://www.blockchain.education/blockchain101/smart-contracts)
|
||||
- [Smart Contracts Introduction](https://chain.link/education/smart-contracts)
|
||||
- [What Is a Smart Contract?](https://chain.link/education/smart-contracts)
|
||||
- [Smart contracts - Simply Explained](https://youtu.be/ZE2HxTmxfrI)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# dApps
|
||||
|
||||
A decentralised application (dApp) is an application that can operate autonomously, through the use of smart contracts that run on a blockchain. Like traditional applications, dApps provide some function or utility to its users.
|
||||
A decentralized application (dApp) is an application that can operate autonomously, through the use of smart contracts that run on a blockchain. Like traditional applications, dApps provide some function or utility to its users.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ seo:
|
||||
- 'code review for beginners'
|
||||
- 'code reviews'
|
||||
- 'code review best practices'
|
||||
- 'code review roadmap 2023'
|
||||
- 'code review roadmap 2024'
|
||||
- 'guide to learning code review'
|
||||
- 'code review roadmap'
|
||||
- 'code review learning path'
|
||||
|
||||
@@ -3,8 +3,8 @@
|
||||
- Does it satisfy the original requirements?
|
||||
- Is it logically correct?
|
||||
- Is there no unnecessary complexity?
|
||||
- Is it robust (no concurrency issues, proper error handling, etc.)?
|
||||
- Is it robust (i.e., no concurrency issues, proper error handling, etc.)?
|
||||
- Is it performant?
|
||||
- Is it secure e.g., no SQL injections, etc?
|
||||
- Is it observable e.g., metrics, logging, tracing, etc.?
|
||||
- Is it secure (i.e., no SQL injections, etc.)?
|
||||
- Is it observable (i.e., metrics, logging, tracing, etc.)?
|
||||
- Do newly added dependencies pull their weight? Is their license acceptable?
|
||||
|
||||
@@ -23,10 +23,10 @@ seo:
|
||||
keywords:
|
||||
- 'computer science roadmap'
|
||||
- 'computer science'
|
||||
- 'computer science roadmap 2023'
|
||||
- 'computer science roadmap 2024'
|
||||
- 'guide to computer science'
|
||||
- 'software engineer roadmap'
|
||||
- 'software engineer roadmap 2023'
|
||||
- 'software engineer roadmap 2024'
|
||||
- 'self-taught computer science roadmap'
|
||||
- 'computer science skills'
|
||||
- 'computer science skills test'
|
||||
|
||||
@@ -10,7 +10,7 @@ Given below is the list of common algorithmic runtimes. The runtimes are listed
|
||||
- O(n^3) - Cubic
|
||||
- O(2^n) - Exponential
|
||||
- O(n!) - Factorial
|
||||
- O(n^n) - Polynomial
|
||||
- O(n^k) - Polynomial
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -10,6 +10,6 @@ Code editors are programs specifically designed for editing, managing and writin
|
||||
|
||||
These are just a few examples, and there are many other code editors available, including Atom, Notepad++, and Geany. They all have their features and may suit different developers' needs. Finding the right code editor is often a matter of personal preference and workflow.
|
||||
|
||||
To work with C++ in your chosen code editor, you often need to install some additional tools and add-ons, such as compilers, linters, and debugger support. Make sure to follow the instructions provided by the editor's documentation to set up C++ correctly.
|
||||
To work with C++ in your chosen code editor, you often need to install some additional tools and add-ons, such as compilers, linters, and debugger support. Make sure to follow the instructions provided in the editor's documentation to set up C++ correctly.
|
||||
|
||||
- [Using C++ on Linux in VSCode](https://code.visualstudio.com/docs/cpp/config-linux)
|
||||
- [Using C++ on Linux in VSCode](https://code.visualstudio.com/docs/cpp/config-linux)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/cpp.json'
|
||||
pdfUrl: '/pdfs/roadmaps/cpp.pdf'
|
||||
order: 10
|
||||
briefTitle: 'C++'
|
||||
briefDescription: 'Step by step guide to becoming a C++ Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a C++ Developer in 2024'
|
||||
title: 'C++ Developer Roadmap'
|
||||
description: 'Step by step guide to becoming a C++ developer in 2023'
|
||||
description: 'Step by step guide to becoming a C++ developer in 2024'
|
||||
isNew: true
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2639.34
|
||||
schema:
|
||||
headline: 'C++ Developer Roadmap'
|
||||
description: 'Learn how to become a C++ Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a C++ Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/cpp.png'
|
||||
datePublished: '2023-06-01'
|
||||
dateModified: '2023-06-01'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/cyber-security.json'
|
||||
pdfUrl: '/pdfs/roadmaps/cyber-security.pdf'
|
||||
order: 11
|
||||
briefTitle: 'Cyber Security'
|
||||
briefDescription: 'Step by step guide to becoming a Cyber Security Expert in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Cyber Security Expert in 2024'
|
||||
title: 'Cyber Security Expert'
|
||||
description: 'Step by step guide to becoming a Cyber Security Expert in 2023'
|
||||
description: 'Step by step guide to becoming a Cyber Security Expert in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 3316.15
|
||||
schema:
|
||||
headline: 'Cyber Security Roadmap: Learn to become a Cyber Security Expert'
|
||||
description: 'Learn how to become a Cyber Security expert with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Cyber Security expert with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/cyber-security.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -14,7 +14,7 @@ dimensions:
|
||||
height: 2309.7
|
||||
schema:
|
||||
headline: 'Design System Roadmap'
|
||||
description: 'Learn how to create a Design System with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to create a Design System with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/design-system.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-19'
|
||||
|
||||
@@ -7,7 +7,7 @@ Here are some of the resources to learn about SSH:
|
||||
- [SSH Intro](https://www.baeldung.com/cs/ssh-intro)
|
||||
- [What is SSH?](https://www.ssh.com/academy/ssh/protocol)
|
||||
- [SFTP using SSH](https://www.goanywhere.com/blog/how-sftp-works)
|
||||
- [OpenSSH Full Guide](https://www.youtube.com/watch?v=ys5zh7kexve)
|
||||
- [OpenSSH Full Guide](https://www.youtube.com/watch?v=YS5Zh7KExvE)
|
||||
|
||||
Visit the following to learn about SSL/TLS:
|
||||
|
||||
@@ -33,4 +33,4 @@ Here are some resources to learn about DNS:
|
||||
- [What is DNS?](https://www.cloudflare.com/en-gb/learning/dns/what-is-dns/)
|
||||
- [HOw DNS works (comic)](https://howdns.works/)
|
||||
- [DNS and How does it Work?](https://www.youtube.com/watch?v=Wj0od2ag5sk)
|
||||
- [DNS Records](https://www.youtube.com/watch?v=7lxgpKh_fRY)
|
||||
- [DNS Records](https://www.youtube.com/watch?v=7lxgpKh_fRY)
|
||||
|
||||
@@ -8,6 +8,8 @@ Visit the following resources to learn more:
|
||||
|
||||
- [AWS Website](https://aws.amazon.com/)
|
||||
- [AWS Documentation](https://docs.aws.amazon.com/)
|
||||
- [AWS Cloud Essentials](https://aws.amazon.com/getting-started/cloud-essentials/)
|
||||
- [Overview of Amazon Web Services](https://docs.aws.amazon.com/whitepapers/latest/aws-overview/introduction.html)
|
||||
- [Sign up for AWS](https://portal.aws.amazon.com/billing/signup)
|
||||
- [How to learn AWS](https://cs.fyi/guide/how-to-learn-aws/)
|
||||
- [AWS Ramp Up Guide](https://d1.awsstatic.com/training-and-certification/ramp-up_guides/Ramp-Up_Guide_CloudPractitioner.pdf)
|
||||
@@ -16,4 +18,4 @@ Visit the following resources to learn more:
|
||||
- [AWS Tutorial for Beginners](https://www.youtube.com/watch?v=k1RI5locZE4&t=129s)
|
||||
- [AWS Course for Beginners](https://www.coursera.org/learn/aws-cloud-technical-essentials?specialization=aws-devops)
|
||||
- [DevOps on AWS Course ](https://www.coursera.org/specializations/aws-devops?#courses)
|
||||
- [AWS Practitioner ](https://youtu.be/SOTamWNgDKc)
|
||||
- [AWS Practitioner ](https://youtu.be/SOTamWNgDKc)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Cloud Providers
|
||||
|
||||
Cloud providers provide a layer of APIs to abstract infrastructure and provision it based on security and billing boundaries. The cloud runs on servers in data centers, but the abstractions cleverly give the appearance of interacting with a single "platform" or large application. The ability to quickly provision, configure and secure resources with cloud providers has been key to both the tremendous success, and complexity, of modern DevOps.
|
||||
Cloud providers provide a layer of APIs to abstract infrastructure and provision it based on security and billing boundaries. The cloud runs on servers in data centers, but the abstractions cleverly give the appearance of interacting with a single “platform” or large application. The ability to quickly provision, configure, and secure resources with cloud providers has been key to both the tremendous success and complexity of modern DevOps.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/devops.json'
|
||||
pdfUrl: '/pdfs/roadmaps/devops.pdf'
|
||||
order: 3
|
||||
briefTitle: 'DevOps'
|
||||
briefDescription: 'Step by step guide for DevOps or operations role in 2023'
|
||||
briefDescription: 'Step by step guide for DevOps or operations role in 2024'
|
||||
title: 'DevOps Roadmap'
|
||||
description: 'Step by step guide for DevOps, SRE or any other Operations Role in 2023'
|
||||
description: 'Step by step guide for DevOps, SRE or any other Operations Role in 2024'
|
||||
hasTopics: true
|
||||
isForkable: true
|
||||
tnsBannerLink: 'https://thenewstack.io?utm_source=roadmap.sh&utm_medium=Referral&utm_campaign=Alert'
|
||||
@@ -31,9 +31,9 @@ seo:
|
||||
title: 'DevOps Roadmap: Learn to become a DevOps Engineer or SRE'
|
||||
description: 'Learn to become a modern DevOps engineer by following the steps, skills, resources and guides listed in our community-driven roadmap.'
|
||||
keywords:
|
||||
- 'devops roadmap 2023'
|
||||
- 'sre roadmap 2023'
|
||||
- 'operations roadmap 2023'
|
||||
- 'devops roadmap 2024'
|
||||
- 'sre roadmap 2024'
|
||||
- 'operations roadmap 2024'
|
||||
- 'guide to becoming a devops engineer'
|
||||
- 'devops roadmap'
|
||||
- 'sre roadmap'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/docker.json'
|
||||
pdfUrl: '/pdfs/roadmaps/docker.pdf'
|
||||
order: 14
|
||||
briefTitle: 'Docker'
|
||||
briefDescription: 'Step by step guide to learning Docker in 2023'
|
||||
briefDescription: 'Step by step guide to learning Docker in 2024'
|
||||
title: 'Docker Roadmap'
|
||||
description: 'Step by step guide to learning Docker in 2023'
|
||||
description: 'Step by step guide to learning Docker in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,13 +13,13 @@ dimensions:
|
||||
height: 1808.98
|
||||
schema:
|
||||
headline: 'Docker Roadmap'
|
||||
description: 'Learn how to use Docker with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to use Docker with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/docker.png'
|
||||
datePublished: '2023-05-10'
|
||||
dateModified: '2023-05-10'
|
||||
seo:
|
||||
title: 'Docker Roadmap - roadmap.sh'
|
||||
description: 'Step by step guide to learn Docker in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Step by step guide to learn Docker in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
keywords:
|
||||
- 'docker tutorial'
|
||||
- 'step by step guide for docker'
|
||||
|
||||
@@ -14,6 +14,5 @@ These control flow statements can be used to create complex logic and control th
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Control flow statements](https://dart.dev/guides/language/language-tour#control-flow-statements)
|
||||
- [Dart Control Flow Statements](https://www.w3adda.com/dart-tutorial/dart-control-flow-statements)
|
||||
- [Branches in Dart](https://dart.dev/language/branches)
|
||||
- [Branches in Dart](https://dart.dev/language/branches)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/flutter.json'
|
||||
pdfUrl: '/pdfs/roadmaps/flutter.pdf'
|
||||
order: 10
|
||||
briefTitle: 'Flutter'
|
||||
briefDescription: 'Step by step guide to becoming a Flutter Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Flutter Developer in 2024'
|
||||
title: 'Flutter Developer'
|
||||
description: 'Step by step guide to becoming a Flutter developer in 2023'
|
||||
description: 'Step by step guide to becoming a Flutter developer in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2042.2
|
||||
schema:
|
||||
headline: 'Flutter Developer Roadmap'
|
||||
description: 'Learn how to become a Flutter Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Flutter Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/flutter.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -4,6 +4,6 @@ Material-UI is an open-source framework that features React components that impl
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Official Website](https://mui.com/)
|
||||
- [Official Documentation](https://mui.com/getting-started/installation/)
|
||||
- [Material UI React Tutorial](https://www.youtube.com/watch?v=vyJU9efvUtQ)
|
||||
- [Official Website](https://mui.com/material-ui/)
|
||||
- [Official Documentation](https://mui.com/material-ui/getting-started/)
|
||||
- [Material UI React Tutorial](https://www.youtube.com/watch?v=o1chMISeTC0)
|
||||
|
||||
@@ -6,3 +6,4 @@ It works with projects using: Babel, TypeScript, Node, React, Angular, Vue and m
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Jest Website](https://jestjs.io/)
|
||||
- [JavaScript Testing With Jest](https://youtu.be/IPiUDhwnZxA?si=2_lE2bDo2fRuo2CU)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/frontend.json'
|
||||
pdfUrl: '/pdfs/roadmaps/frontend.pdf'
|
||||
order: 1
|
||||
briefTitle: 'Frontend'
|
||||
briefDescription: 'Step by step guide to becoming a frontend developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a frontend developer in 2024'
|
||||
title: 'Frontend Developer'
|
||||
description: 'Step by step guide to becoming a modern frontend developer in 2023'
|
||||
description: 'Step by step guide to becoming a modern frontend developer in 2024'
|
||||
hasTopics: true
|
||||
isForkable: true
|
||||
tnsBannerLink: 'https://thenewstack.io?utm_source=roadmap.sh&utm_medium=Referral&utm_campaign=Alert'
|
||||
@@ -29,9 +29,9 @@ seo:
|
||||
title: 'Frontend Developer Roadmap: What is Frontend Development?'
|
||||
description: 'Learn what Frontend Development is, what frontend developers do and how to become a modern frontend developer using our community-driven roadmap.'
|
||||
keywords:
|
||||
- 'javascript roadmap 2023'
|
||||
- 'frontend roadmap 2023'
|
||||
- 'frontend developer roadmap 2023'
|
||||
- 'javascript roadmap 2024'
|
||||
- 'frontend roadmap 2024'
|
||||
- 'frontend developer roadmap 2024'
|
||||
- 'guide to becoming a developer'
|
||||
- 'guide to becoming a frontend developer'
|
||||
- 'frontend developer'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/full-stack.json'
|
||||
pdfUrl: '/pdfs/roadmaps/full-stack.pdf'
|
||||
order: 3
|
||||
briefTitle: 'Full Stack'
|
||||
briefDescription: 'Step by step guide to becoming a full stack developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a full stack developer in 2024'
|
||||
title: 'Full Stack Developer'
|
||||
description: 'Step by step guide to becoming a modern full stack developer in 2023'
|
||||
description: 'Step by step guide to becoming a modern full stack developer in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -17,7 +17,7 @@ question:
|
||||
Full stack development is the practice of being proficient in both the front-end and back-end aspects of web application development. A full stack developer is capable of working on all layers of a software application, from the user interface and user experience (front-end) to the server, database, and server-side logic (back-end). This versatility allows them to create and maintain complete web applications independently or as part of a development team.
|
||||
schema:
|
||||
headline: 'Full Stack Developer Roadmap'
|
||||
description: 'Learn how to become a Full Stack Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Full Stack Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/full-stack.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
@@ -25,9 +25,9 @@ seo:
|
||||
title: 'Full Stack Developer Roadmap'
|
||||
description: 'Learn to become a modern full stack developer using this roadmap. Community driven, articles, resources, guides, interview questions, quizzes for modern full stack development.'
|
||||
keywords:
|
||||
- 'javascript roadmap 2023'
|
||||
- 'full stack roadmap 2023'
|
||||
- 'full stack developer roadmap 2023'
|
||||
- 'javascript roadmap 2024'
|
||||
- 'full stack roadmap 2024'
|
||||
- 'full stack developer roadmap 2024'
|
||||
- 'guide to becoming a developer'
|
||||
- 'guide to becoming a full stack developer'
|
||||
- 'full stack developer'
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
# Curve
|
||||
# Orientation
|
||||
|
||||
In the context of game development, **Orientation** refers to the aspect or direction in which an object is pointed in a 3D space. To determine an object's orientation in 3D space, we typically use three angles namely: pitch, yaw, and roll collectively known as Euler's angles. **Pitch** is the rotation around the X-axis, **Yaw** around the Y-axis and **Roll** around the Z-axis. Alternatively, orientation can also be represented using a Quaternion. Quaternions have the advantage of avoiding a problem known as Gimbal lock (a loss of one degree of freedom in 3D space), present when using Euler's angles.
|
||||
In the context of game development, **Orientation** refers to the aspect or direction in which an object is pointed in a 3D space. To determine an object's orientation in 3D space, we typically use three angles namely: pitch, yaw, and roll collectively known as Euler's angles. **Pitch** is the rotation around the X-axis, **Yaw** around the Y-axis and **Roll** around the Z-axis. Alternatively, orientation can also be represented using a Quaternion. Quaternions have the advantage of avoiding a problem known as Gimbal lock (a loss of one degree of freedom in 3D space), present when using Euler's angles.
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
pdfUrl: '/pdfs/roadmaps/game-developer.pdf'
|
||||
order: 17
|
||||
briefTitle: 'Game Developer'
|
||||
briefDescription: 'Roadmap to becoming a Game Developer in 2023'
|
||||
briefDescription: 'Roadmap to becoming a Game Developer in 2024'
|
||||
title: 'Game Developer'
|
||||
description: 'Roadmap to becoming a Game Developer in 2023'
|
||||
description: 'Roadmap to becoming a Game Developer in 2024'
|
||||
hasTopics: true
|
||||
isNew: true
|
||||
dimensions:
|
||||
@@ -20,8 +20,8 @@ seo:
|
||||
title: 'Game Developer Roadmap'
|
||||
description: 'Learn what game development is, what game developers do and how to become one using our community-driven roadmap.'
|
||||
keywords:
|
||||
- 'game developer roadmap 2023'
|
||||
- 'game developer roadmap 2023'
|
||||
- 'game developer roadmap 2024'
|
||||
- 'game developer roadmap 2024'
|
||||
- 'guide to becoming a developer'
|
||||
- 'guide to becoming a game developer'
|
||||
- 'game developer roadmap'
|
||||
|
||||
@@ -3,16 +3,16 @@ jsonUrl: '/jsons/roadmaps/golang.json'
|
||||
pdfUrl: '/pdfs/roadmaps/golang.pdf'
|
||||
order: 11
|
||||
briefTitle: 'Go'
|
||||
briefDescription: 'Step by step guide to becoming a Go developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Go developer in 2024'
|
||||
title: 'Go Developer'
|
||||
description: 'Step by step guide to becoming a Go developer in 2023'
|
||||
description: 'Step by step guide to becoming a Go developer in 2024'
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
width: 968
|
||||
height: 1495.21
|
||||
schema:
|
||||
headline: 'Go Developer Roadmap'
|
||||
description: 'Learn how to become a Go Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Go Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/golang.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/graphql.json'
|
||||
pdfUrl: '/pdfs/roadmaps/graphql.pdf'
|
||||
order: 12
|
||||
briefTitle: 'GraphQL'
|
||||
briefDescription: 'Step by Step guide to learn GraphQL in 2023'
|
||||
briefDescription: 'Step by Step guide to learn GraphQL in 2024'
|
||||
title: 'GraphQL'
|
||||
description: 'Step by step guide to learn GraphQL in 2023'
|
||||
description: 'Step by step guide to learn GraphQL in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 1669.8
|
||||
schema:
|
||||
headline: 'GraphQL Roadmap'
|
||||
description: 'Learn how to use GraphQL with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to use GraphQL with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/graphql.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -3,16 +3,16 @@ jsonUrl: '/jsons/roadmaps/java.json'
|
||||
pdfUrl: '/pdfs/roadmaps/java.pdf'
|
||||
order: 9
|
||||
briefTitle: 'Java'
|
||||
briefDescription: 'Step by step guide to becoming a Java Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Java Developer in 2024'
|
||||
title: 'Java Developer'
|
||||
description: 'Step by step guide to becoming a Java developer in 2023'
|
||||
description: 'Step by step guide to becoming a Java developer in 2024'
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
width: 968
|
||||
height: 1167.29
|
||||
schema:
|
||||
headline: 'Java Developer Roadmap'
|
||||
description: 'Learn how to become a Java Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Java Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/java.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
# Javascript Versions
|
||||
|
||||
JavaScript was invented by Brendan Eich, and in 1997 it became an ECMA standard. ECMAScript is the official language name. ECMAScript versions include ES1, ES2, ES3, ES5, and ES6
|
||||
JavaScript, invented by Brendan Eich, achieved the status of an ECMA standard in 1997 and adopted the official name ECMAScript. This language has evolved through several versions, namely ES1, ES2, ES3, ES5, and the transformative ES6. These updates have played a crucial role in improving and standardizing JavaScript, making it widely used and valuable in the ever-changing field of web development.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [JavaScript Versions: How JavaScript has changed over the years](https://www.educative.io/blog/javascript-versions-history)
|
||||
- [Brief History of JavaScript](https://roadmap.sh/guides/history-of-javascript)
|
||||
- [JavaScript Version](https://www.w3schools.com/js/js_versions.asp)
|
||||
|
||||
@@ -5,4 +5,4 @@ In JavaScript, all exceptions are simply objects. While the majority of exceptio
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Throwing Exceptions in JavaScript](https://rollbar.com/guides/javascript/how-to-throw-exceptions-in-javascript)
|
||||
- [try, catch, finally, throw (video)](https://youtu.be/cftftueq-10)
|
||||
- [try, catch, finally, throw (video)](https://youtu.be/cFTFtuEQ-10)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Expressions and Operators
|
||||
|
||||
At a high level, an expression is a valid unit of code that resolves to a value. There are two types of expressions: those that have side effects (such as assigning values) and those that purely evaluate. The expression `x = 7` is an example of the first type. This expression uses the `=` operator to assign the value seven to the variable x. The expression itself evaluates to 7. The expression `3 + 4` is an example of the second type. This expression uses the `+` operator to add `3` and `4` together and produces a value, `7`. However, if it's not eventually part of a bigger construct (for example, a variable declaration like const `z = 3 + 4`), its result will be immediately discarded `—` this is usually a programmer mistake because the evaluation doesn't produce any effects. As the examples above also illustrate, all complex expressions are joined by operators, such as `=` and `+`.
|
||||
At a high level, an expression is a valid unit of code that resolves to a value. There are two types of expressions: those that have side effects (such as assigning values) and those that purely evaluate. The expression `x = 7` is an example of the first type. This expression uses the `=` operator to assign the value seven to the variable x. The expression itself evaluates to 7. The expression `3 + 4` is an example of the second type. This expression uses the `+` operator to add `3` and `4` together and produces a value, `7`. However, if it's not eventually part of a bigger construct (for example, a variable declaration like `const z = 3 + 4`), its result will be immediately discarded `—` this is usually a programmer mistake because the evaluation doesn't produce any effects. As the examples above also illustrate, all complex expressions are joined by operators, such as `=` and `+`.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/javascript.json'
|
||||
pdfUrl: '/pdfs/roadmaps/javascript.pdf'
|
||||
order: 5
|
||||
briefTitle: 'JavaScript'
|
||||
briefDescription: 'Step by step guide to learn JavaScript in 2023'
|
||||
briefDescription: 'Step by step guide to learn JavaScript in 2024'
|
||||
title: 'JavaScript Roadmap'
|
||||
description: 'Step by step guide to learn JavaScript in 2023'
|
||||
description: 'Step by step guide to learn JavaScript in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2438.9
|
||||
schema:
|
||||
headline: 'JavaScript Roadmap'
|
||||
description: 'Learn JavaScript with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn JavaScript with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/javascript.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
@@ -21,11 +21,11 @@ seo:
|
||||
title: 'JavaScript Developer Roadmap: Step by step guide to learn JavaScript'
|
||||
description: 'Community driven, articles, resources, guides, interview questions, quizzes for javascript development. Learn to become a modern JavaScript developer by following the steps, skills, resources and guides listed in this roadmap.'
|
||||
keywords:
|
||||
- 'javascript guide 2023'
|
||||
- 'javascript guide 2024'
|
||||
- 'learn javascript'
|
||||
- 'step by step javascript guide'
|
||||
- 'javascript roadmap 2023'
|
||||
- 'javascript developer roadmap 2023'
|
||||
- 'javascript roadmap 2024'
|
||||
- 'javascript developer roadmap 2024'
|
||||
- 'guide to becoming a javascript developer'
|
||||
- 'javascript developer roadmap'
|
||||
- 'javascript roadmap'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/kubernetes.json'
|
||||
pdfUrl: '/pdfs/roadmaps/kubernetes.pdf'
|
||||
order: 14
|
||||
briefTitle: 'Kubernetes'
|
||||
briefDescription: 'Step by step guide to learning Kubernetes in 2023'
|
||||
briefDescription: 'Step by step guide to learning Kubernetes in 2024'
|
||||
title: 'Kubernetes Roadmap'
|
||||
description: 'Step by step guide to learning Kubernetes in 2023'
|
||||
description: 'Step by step guide to learning Kubernetes in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
tnsBannerLink: 'https://thenewstack.io/kubernetes?utm_source=roadmap.sh&utm_medium=Referral&utm_campaign=Alert'
|
||||
@@ -14,17 +14,17 @@ dimensions:
|
||||
height: 1785.73
|
||||
schema:
|
||||
headline: 'Kubernetes Roadmap'
|
||||
description: 'Learn how to use Kubernetes with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to use Kubernetes with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/kubernetes.png'
|
||||
datePublished: '2023-05-04'
|
||||
dateModified: '2023-05-04'
|
||||
seo:
|
||||
title: 'Kubernetes Roadmap - roadmap.sh'
|
||||
description: 'Step by step guide to learn Kubernetes in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Step by step guide to learn Kubernetes in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
keywords:
|
||||
- 'kubernetes tutorial'
|
||||
- 'step by step kubernetes'
|
||||
- 'kubernetes roadmap 2023'
|
||||
- 'kubernetes roadmap 2024'
|
||||
- 'guide to learning kubernetes'
|
||||
- 'kubernetes roadmap'
|
||||
- 'kubernetes'
|
||||
|
||||
@@ -30,20 +30,6 @@ db.users.deleteMany({ country: 'Australia' });
|
||||
|
||||
This command will delete all `users` documents with a `country` field equal to `"Australia"`.
|
||||
|
||||
## db.collection.remove()
|
||||
|
||||
The `remove()` method can be used to delete documents in a more flexible way, as it takes both a filter and a `justOne` option. If `justOne` is set to true, only the first document (by natural order) that matches the filter will be removed. Otherwise, if `justOne` is set to false, all documents matching the filter will be deleted.
|
||||
|
||||
Syntax: `db.collection.remove(FILTER, JUST_ONE)`
|
||||
|
||||
Example:
|
||||
|
||||
```javascript
|
||||
db.users.remove({ age: { $lt: 18 } }, true);
|
||||
```
|
||||
|
||||
This command would delete a single user document with an `age` field value less than 18.
|
||||
|
||||
## db.collection.drop()
|
||||
|
||||
In cases where you want to remove an entire collection, including the documents and the metadata, you can use the `drop()` method. This command does not require a filter, as it removes everything in the specified collection.
|
||||
|
||||
@@ -3,27 +3,27 @@ jsonUrl: '/jsons/roadmaps/mongodb.json'
|
||||
pdfUrl: '/pdfs/roadmaps/mongodb.pdf'
|
||||
order: 14
|
||||
briefTitle: 'MongoDB'
|
||||
briefDescription: 'Step by step guide to learning MongoDB in 2023'
|
||||
briefDescription: 'Step by step guide to learning MongoDB in 2024'
|
||||
title: 'MongoDB Roadmap'
|
||||
description: 'Step by step guide to learning MongoDB in 2023'
|
||||
description: 'Step by step guide to learning MongoDB in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
width: 968
|
||||
height: 2123.45
|
||||
schema:
|
||||
headline: 'MongoDB Roadmap: Step by step guide to learning MongoDB in 2023'
|
||||
headline: 'MongoDB Roadmap: Step by step guide to learning MongoDB in 2024'
|
||||
description: 'Learn how to use MongoDB with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/mongodb.png'
|
||||
datePublished: '2023-03-16'
|
||||
dateModified: '2023-03-16'
|
||||
seo:
|
||||
title: 'MongoDB Roadmap - roadmap.sh'
|
||||
description: 'Step by step guide to learn MongoDB in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Step by step guide to learn MongoDB in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
keywords:
|
||||
- 'mongodb tutorial'
|
||||
- 'step by step mongodb'
|
||||
- 'mongodb roadmap 2023'
|
||||
- 'mongodb roadmap 2024'
|
||||
- 'guide to learning mongodb'
|
||||
- 'mongodb roadmap'
|
||||
- 'mongodb'
|
||||
|
||||
@@ -6,8 +6,8 @@ It is two things: first and foremost, it is an online repository for the publish
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [What is npm?](https://nodejs.dev/en/learn/an-introduction-to-the-npm-package-manager/)
|
||||
- [An introduction to the npm package manager](https://nodejs.dev/en/learn/an-introduction-to-the-npm-package-manager/)
|
||||
- [What is npm?](https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager)
|
||||
- [An introduction to the npm package manager](https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager)
|
||||
- [Official Website](https://www.npmjs.com/)
|
||||
- [Official Documentation](https://docs.npmjs.com/)
|
||||
- [NPM Crash Course](https://www.youtube.com/watch?v=jHDhaSSKmB0)
|
||||
|
||||
@@ -5,4 +5,4 @@ Taking note of nowadays multicore system single threading is very memory efficie
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Single Thread vs Child Process vs Worker Threads vs Clutster in Node.js](https://alvinlal.netlify.app/blog/single-thread-vs-child-process-vs-worker-threads-vs-cluster-in-nodejs)
|
||||
- [Single Thread vs Child Process vs Worker Threads vs Cluster in Node.js](https://alvinlal.netlify.app/blog/single-thread-vs-child-process-vs-worker-threads-vs-cluster-in-nodejs)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/nodejs.json'
|
||||
pdfUrl: '/pdfs/roadmaps/nodejs.pdf'
|
||||
order: 6
|
||||
briefTitle: 'Node.js'
|
||||
briefDescription: 'Step by step guide to becoming a Node.js developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Node.js developer in 2024'
|
||||
title: 'Node.js Developer'
|
||||
description: 'Step by step guide to becoming a modern Node.js developer in 2023'
|
||||
description: 'Step by step guide to becoming a modern Node.js developer in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2474.06
|
||||
schema:
|
||||
headline: 'Node.js Roadmap'
|
||||
description: 'Learn Node.js with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn Node.js with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/nodejs.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
@@ -21,12 +21,12 @@ seo:
|
||||
title: 'Node.js Developer Roadmap: Learn to become a modern node.js developer'
|
||||
description: 'Learn to become a modern node.js developer using this roadmap. Community driven, articles, resources, guides, interview questions, quizzes for modern node.js development.'
|
||||
keywords:
|
||||
- 'node.js roadmap 2023'
|
||||
- 'nodejs roadmap 2023'
|
||||
- 'node.js roadmap 2023'
|
||||
- 'nodejs roadmap 2023'
|
||||
- 'node.js developer roadmap 2023'
|
||||
- 'nodejs developer roadmap 2023'
|
||||
- 'node.js roadmap 2024'
|
||||
- 'nodejs roadmap 2024'
|
||||
- 'node.js roadmap 2024'
|
||||
- 'nodejs roadmap 2024'
|
||||
- 'node.js developer roadmap 2024'
|
||||
- 'nodejs developer roadmap 2024'
|
||||
- 'guide to becoming a developer'
|
||||
- 'guide to becoming a node.js developer'
|
||||
- 'guid to becoming a node.js developer'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/postgresql-dba.json'
|
||||
pdfUrl: '/pdfs/roadmaps/postgresql-dba.pdf'
|
||||
order: 5
|
||||
briefTitle: 'PostgreSQL'
|
||||
briefDescription: 'Step by step guide to become a PostgreSQL DBA in 2023'
|
||||
briefDescription: 'Step by step guide to become a PostgreSQL DBA in 2024'
|
||||
title: 'PostgreSQL DBA'
|
||||
description: 'Step by step guide to becoming a modern PostgreSQL DB Administrator in 2023'
|
||||
description: 'Step by step guide to becoming a modern PostgreSQL DB Administrator in 2024'
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
width: 969
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# How are LLMs Built?
|
||||
|
||||
On a high level, training an LLM model involves thre steps i.e. data collection, training and evaluation.
|
||||
On a high level, training an LLM model involves three steps i.e. data collection, training and evaluation.
|
||||
|
||||
- **Data Collection** The first step is to collect the data that will be used to train the model. The data can be collected from various sources such as Wikipedia, news articles, books, websites etc.
|
||||
|
||||
@@ -8,4 +8,4 @@ On a high level, training an LLM model involves thre steps i.e. data collection,
|
||||
|
||||
- **Evaluation**: The final step is to evaluate the performance of the model to see how well it performs on various tasks such as question answering, summarization, translation etc.
|
||||
|
||||
The output from the training Pipeline is an LLM model which is simply the parameters or weights which capture the knowledge learned during the training process. These parameters or weights are typically serialized and stored in a file, which can then be loaded into any application that requires language processing capabilities e.g. text generation, question answering, language processing etc.
|
||||
The output from the training Pipeline is an LLM model which is simply the parameters or weights which capture the knowledge learned during the training process. These parameters or weights are typically serialized and stored in a file, which can then be loaded into any application that requires language processing capabilities e.g. text generation, question answering, language processing etc.
|
||||
|
||||
@@ -18,7 +18,7 @@ When working with LLMs, you will come across a lot of new terms. This section wi
|
||||
|
||||
- **Label Distribution** — The label distribution is the probability distribution over the label space. For example, if you have a text that says "I love you", then the label distribution could be [0.8, 0.1, 0.1]. This means that the model thinks there is an 80% chance that the text is positive, a 10% chance that it is negative, and a 10% chance that it is neutral.
|
||||
|
||||
- **Sentiment Analysis** — Sentiment analysis is the process of determining the emotional tone behind a series of words, used to gain an understanding of the the attitudes, opinions and emotions expressed within an online mention. Sentiment analysis is also known as opinion mining, deriving the opinion or attitude of a speaker.
|
||||
- **Sentiment Analysis** — Sentiment analysis is the process of determining the emotional tone behind a series of words, used to gain an understanding of the attitudes, opinions and emotions expressed within an online mention. Sentiment analysis is also known as opinion mining, deriving the opinion or attitude of a speaker.
|
||||
|
||||
- **Verbalizer** — In the classification setting, verbalizers are mappings from labels to words in a language model's vocabulary. For example, consider performing sentiment classification with the following prompt:
|
||||
```
|
||||
@@ -31,4 +31,4 @@ When working with LLMs, you will come across a lot of new terms. This section wi
|
||||
|
||||
References and further learning:
|
||||
|
||||
- [LLM Vocabulary](https://learnprompting.org/docs/vocabulary)
|
||||
- [LLM Vocabulary](https://learnprompting.org/docs/vocabulary)
|
||||
|
||||
@@ -22,7 +22,7 @@ seo:
|
||||
keywords:
|
||||
- 'prompt engineering tutorial'
|
||||
- 'step by step prompt engineering'
|
||||
- 'prompt engineering roadmap 2023'
|
||||
- 'prompt engineering roadmap 2024'
|
||||
- 'guide to learning prompt engineering'
|
||||
- 'prompt engineering roadmap'
|
||||
- 'prompt engineering'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Flask
|
||||
|
||||
Flask is a micro web framework written in Python. It is classified as a microframework because it does not require particular tools or libraries. It has no database abstraction layer, form validation, or any other components where pre-existing third-party libraries provide common functions.
|
||||
Flask is a micro web framework written in Python. It is classified as a microframework because it does not require particular tools or libraries. It has no database abstraction layer, form validation, or any other components where pre-existing third-party libraries provide common functions. Instead, it provides flexibility by requiring you to choose and integrate the best libraries for your project's needs.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
|
||||
@@ -3,16 +3,16 @@ jsonUrl: '/jsons/roadmaps/python.json'
|
||||
pdfUrl: '/pdfs/roadmaps/python.pdf'
|
||||
order: 7
|
||||
briefTitle: 'Python'
|
||||
briefDescription: 'Step by step guide to becoming a Python Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Python Developer in 2024'
|
||||
title: 'Python Developer'
|
||||
description: 'Step by step guide to becoming a Python developer in 2023'
|
||||
description: 'Step by step guide to becoming a Python developer in 2024'
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
width: 992
|
||||
height: 1259.03
|
||||
schema:
|
||||
headline: 'Python Roadmap'
|
||||
description: 'Learn Python with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn Python with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/python.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/qa.json'
|
||||
pdfUrl: '/pdfs/roadmaps/qa.pdf'
|
||||
order: 7
|
||||
briefTitle: 'QA'
|
||||
briefDescription: 'Step by step guide to becoming a modern QA Engineer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a modern QA Engineer in 2024'
|
||||
title: 'QA Engineer'
|
||||
description: 'Steps to follow in order to become a modern QA Engineer in 2023'
|
||||
description: 'Steps to follow in order to become a modern QA Engineer in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2107.75
|
||||
schema:
|
||||
headline: 'QA Engineer Roadmap'
|
||||
description: 'Learn to become a QA Engineer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn to become a QA Engineer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/qa.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
order: 13
|
||||
briefTitle: 'React Native'
|
||||
briefDescription: 'Step by step guide to becoming a React Native Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a React Native Developer in 2024'
|
||||
title: 'React Native Developer'
|
||||
description: 'Step by step guide to becoming a React Native developer in 2023'
|
||||
description: 'Step by step guide to becoming a React Native developer in 2024'
|
||||
pdfUrl: '/pdfs/roadmaps/react-native.pdf'
|
||||
hasTopics: true
|
||||
isNew: false
|
||||
@@ -12,7 +12,7 @@ dimensions:
|
||||
height: 2333.39
|
||||
schema:
|
||||
headline: 'React Native Roadmap'
|
||||
description: 'Learn how to become a React Native Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a React Native Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/react-native.png'
|
||||
datePublished: '2023-06-27'
|
||||
dateModified: '2023-06-27'
|
||||
|
||||
@@ -10,3 +10,4 @@ Visit the following resources to learn more:
|
||||
|
||||
- [High-Order Components](https://reactjs.org/docs/higher-order-components.html)
|
||||
- [How to create a Higher-Order Component](https://www.robinwieruch.de/react-higher-order-components/)
|
||||
- [Learn React Higher Order Component (HOC) in 10 Minutes](https://youtu.be/J5P0q7EROfw?si=-8s5h1b0mZSGVgLt)
|
||||
|
||||
@@ -4,6 +4,6 @@ Material-UI is an open-source framework that features React components that impl
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Official Website](https://mui.com/)
|
||||
- [Official Documentation](https://mui.com/getting-started/installation/)
|
||||
- [Material UI React Tutorial](https://www.youtube.com/watch?v=vyJU9efvUtQ)
|
||||
- [Official Website](https://mui.com/material-ui/)
|
||||
- [Official Documentation](https://mui.com/material-ui/getting-started/)
|
||||
- [Material UI React Tutorial](https://www.youtube.com/watch?v=o1chMISeTC0)
|
||||
|
||||
@@ -4,5 +4,5 @@ Small progressive client-side HTTP request library, and Node.js module with the
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [Official Website](https://visionmedia.github.io/superagent/)
|
||||
- [Official Website](https://ladjs.github.io/superagent)
|
||||
- [GitHub Repository](https://github.com/visionmedia/superagent)
|
||||
|
||||
@@ -3,16 +3,16 @@ jsonUrl: '/jsons/roadmaps/react.json'
|
||||
pdfUrl: '/pdfs/roadmaps/react.pdf'
|
||||
order: 2
|
||||
briefTitle: 'React'
|
||||
briefDescription: 'Step by step guide to become a React Developer in 2023'
|
||||
briefDescription: 'Step by step guide to become a React Developer in 2024'
|
||||
title: 'React Developer'
|
||||
description: 'Everything that is there to learn about React and the ecosystem in 2023.'
|
||||
description: 'Everything that is there to learn about React and the ecosystem in 2024.'
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
width: 968
|
||||
height: 1570.26
|
||||
schema:
|
||||
headline: 'React Developer Roadmap'
|
||||
description: 'Learn to become a React developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn to become a React developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/react.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
@@ -20,8 +20,8 @@ seo:
|
||||
title: 'React Developer Roadmap: Learn to become a React developer'
|
||||
description: 'Community driven, articles, resources, guides, interview questions, quizzes for react development. Learn to become a modern React developer by following the steps, skills, resources and guides listed in this roadmap.'
|
||||
keywords:
|
||||
- 'react roadmap 2023'
|
||||
- 'react developer roadmap 2023'
|
||||
- 'react roadmap 2024'
|
||||
- 'react developer roadmap 2024'
|
||||
- 'guide to becoming a react developer'
|
||||
- 'react developer roadmap'
|
||||
- 'react roadmap'
|
||||
|
||||
@@ -1,3 +1,8 @@
|
||||
# Variables, Constants, and Data Types
|
||||
|
||||
In Rust, variables are declared using the `let` keyword. They are immutable by default, which means once a value is bound to a variable, it cannot be changed. If you want to make a variable mutable, the `mut` keyword is used. So, if you wanted to declare a mutable variable `x` and assign it the value `5`, you would write `let mut x = 5;`. Variables can also be patterned. By default in Rust, variables are block-scoped. Rust also supports several types of variable attributes.
|
||||
In Rust, variables are declared using the `let` keyword. They are immutable by default, which means once a value is bound to a variable, it cannot be changed. If you want to make a variable mutable, the `mut` keyword is used. So, if you wanted to declare a mutable variable `x` and assign it the value `5`, you would write `let mut x = 5;`. Variables can also be patterned. By default in Rust, variables are block-scoped. Rust also supports several types of variable attributes.
|
||||
|
||||
Learn more from the following links:
|
||||
|
||||
- [Variables and Mutability](https://rust-book.cs.brown.edu/ch03-01-variables-and-mutability.html)
|
||||
- [Data Types](https://rust-book.cs.brown.edu/ch03-02-data-types.html)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/rust.json'
|
||||
pdfUrl: '/pdfs/roadmaps/rust.pdf'
|
||||
order: 11
|
||||
briefTitle: 'Rust'
|
||||
briefDescription: 'Step by step guide to becoming a Rust developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Rust developer in 2024'
|
||||
title: 'Rust Developer'
|
||||
description: 'Step by step guide to becoming a Rust developer in 2023'
|
||||
description: 'Step by step guide to becoming a Rust developer in 2024'
|
||||
hasTopics: true
|
||||
isNew: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2220.4
|
||||
schema:
|
||||
headline: 'Rust Developer Roadmap'
|
||||
description: 'Learn how to become a Rust Developer with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn how to become a Rust Developer with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/rust.png'
|
||||
datePublished: '2023-11-14'
|
||||
dateModified: '2023-11-14'
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
pdfUrl: '/pdfs/roadmaps/server-side-game-developer.pdf'
|
||||
order: 17
|
||||
briefTitle: 'Server Side Game Developer'
|
||||
briefDescription: 'Roadmap to becoming a Server Side Game Developer in 2023'
|
||||
briefDescription: 'Roadmap to becoming a Server Side Game Developer in 2024'
|
||||
title: 'Server Side Game Developer'
|
||||
description: 'Roadmap to becoming a Server Side Game Developer in 2023'
|
||||
description: 'Roadmap to becoming a Server Side Game Developer in 2024'
|
||||
hasTopics: true
|
||||
isNew: true
|
||||
isHidden: true
|
||||
@@ -21,8 +21,8 @@ seo:
|
||||
title: 'Server Side Game Developer Roadmap'
|
||||
description: 'Learn what Server Side Game Development is, what server side game developers do and how to become one using our community-driven roadmap.'
|
||||
keywords:
|
||||
- 'server side game developer roadmap 2023'
|
||||
- 'server side game developer roadmap 2023'
|
||||
- 'server side game developer roadmap 2024'
|
||||
- 'server side game developer roadmap 2024'
|
||||
- 'guide to becoming a server side game developer'
|
||||
- 'guide to becoming a server side game developer'
|
||||
- 'server side game developer roadmap'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/software-architect.json'
|
||||
pdfUrl: '/pdfs/roadmaps/software-architect.pdf'
|
||||
order: 8
|
||||
briefTitle: 'Software Architect'
|
||||
briefDescription: 'Step by step guide to become a Software Architect in 2023'
|
||||
briefDescription: 'Step by step guide to become a Software Architect in 2024'
|
||||
title: 'Software Architect'
|
||||
description: 'Step by step guide to becoming a Software Architect in 2023'
|
||||
description: 'Step by step guide to becoming a Software Architect in 2024'
|
||||
isNew: false
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 1882.18
|
||||
schema:
|
||||
headline: 'Software Architect Roadmap'
|
||||
description: 'Learn to become a Software Architect with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn to become a Software Architect with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/software-architect.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 1764.66
|
||||
schema:
|
||||
headline: 'Software Design and Architecture Roadmap'
|
||||
description: 'Learn Software Design and Architecture with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn Software Design and Architecture with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/software-design-architecture.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/spring-boot.json'
|
||||
pdfUrl: '/pdfs/roadmaps/spring-boot.pdf'
|
||||
order: 10
|
||||
briefTitle: 'Spring Boot'
|
||||
briefDescription: 'Step by step guide to becoming a Spring Boot Developer in 2023'
|
||||
briefDescription: 'Step by step guide to becoming a Spring Boot Developer in 2024'
|
||||
title: 'Spring Boot Developer'
|
||||
description: 'Step by step guide to becoming a Spring Boot developer in 2023'
|
||||
description: 'Step by step guide to becoming a Spring Boot developer in 2024'
|
||||
hasTopics: true
|
||||
isNew: false
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 1245.52
|
||||
schema:
|
||||
headline: 'Spring Boot Roadmap'
|
||||
description: 'Learn Spring Boot with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn Spring Boot with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/spring-boot.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/sql.json'
|
||||
pdfUrl: '/pdfs/roadmaps/sql.pdf'
|
||||
order: 8
|
||||
briefTitle: 'SQL'
|
||||
briefDescription: 'Step by step guide to learning SQL in 2023'
|
||||
briefDescription: 'Step by step guide to learning SQL in 2024'
|
||||
title: 'SQL Roadmap'
|
||||
description: 'Step by step guide to learning SQL in 2023'
|
||||
description: 'Step by step guide to learning SQL in 2024'
|
||||
isNew: true
|
||||
hasTopics: true
|
||||
dimensions:
|
||||
@@ -13,13 +13,13 @@ dimensions:
|
||||
height: 2116.16
|
||||
schema:
|
||||
headline: 'SQL Roadmap'
|
||||
description: 'Comprehensive roadmap to learn SQL from scratch in 2023. From basic syntax to advanced querying, this step-by-step guide will equip you with the skills needed to excel in database management and data analysis.'
|
||||
description: 'Comprehensive roadmap to learn SQL from scratch in 2024. From basic syntax to advanced querying, this step-by-step guide will equip you with the skills needed to excel in database management and data analysis.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/sql.png'
|
||||
datePublished: '2023-07-10'
|
||||
dateModified: '2023-07-10'
|
||||
seo:
|
||||
title: 'SQL Roadmap - roadmap.sh'
|
||||
description: 'Comprehensive roadmap to learn SQL from scratch in 2023. From basic syntax to advanced querying, this step-by-step guide will equip you with the skills needed to excel in database management and data analysis.'
|
||||
description: 'Comprehensive roadmap to learn SQL from scratch in 2024. From basic syntax to advanced querying, this step-by-step guide will equip you with the skills needed to excel in database management and data analysis.'
|
||||
ogImageUrl: 'https://roadmap.sh/og-images/sql-roadmap.png'
|
||||
keywords:
|
||||
- 'sql tutorial'
|
||||
@@ -27,7 +27,7 @@ seo:
|
||||
- 'sql for beginners'
|
||||
- 'how to learn sql'
|
||||
- 'use sql in production'
|
||||
- 'sql roadmap 2023'
|
||||
- 'sql roadmap 2024'
|
||||
- 'guide to learning sql'
|
||||
- 'sql roadmap'
|
||||
- 'sql learning path'
|
||||
|
||||
@@ -5,4 +5,4 @@ Systems such as [Consul](https://www.consul.io/docs/index.html), [Etcd](https://
|
||||
Visit the following links to learn more:
|
||||
|
||||
- [What is Service-oriented architecture?](https://en.wikipedia.org/wiki/Service-oriented_architecture)
|
||||
- [Intro to Service Discovery](https://github.com/donnemartin/system-design-primer#Service%20Discovery)
|
||||
- [Intro to Service Discovery](https://github.com/donnemartin/system-design-primer#Service-Discovery)
|
||||
|
||||
@@ -6,7 +6,7 @@ NoSQL databases, such as MongoDB and Cassandra, are best suited for unstructured
|
||||
|
||||
The choice between SQL and NoSQL depends on the specific use case and requirements of the project. If you need to store and query structured data with complex relationships, an SQL database is likely a better choice. If you need to store and query large amounts of unstructured data with high scalability and performance, a NoSQL database may be a better choice.
|
||||
|
||||
Learn more from the followinw links:
|
||||
Learn more from the following links:
|
||||
|
||||
- [SQL vs NoSQL: The Differences](https://www.sitepoint.com/sql-vs-nosql-differences/)
|
||||
- [SQL vs NoSQL - When to Use Each](https://www.ibm.com/cloud/blog/sql-vs-nosql)
|
||||
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 2848.5
|
||||
schema:
|
||||
headline: 'System Design Roadmap'
|
||||
description: 'Learn System Design with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn System Design with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/system-design.png'
|
||||
datePublished: '2023-01-17'
|
||||
dateModified: '2023-01-17'
|
||||
|
||||
@@ -20,7 +20,7 @@ seo:
|
||||
title: 'Technical Writer Roadmap'
|
||||
description: 'Learn what technical writing is, what technical writers do and how to become one using our community-driven roadmap.'
|
||||
keywords:
|
||||
- 'technical writer roadmap 2023'
|
||||
- 'technical writer roadmap 2024'
|
||||
- 'guide to becoming a technical writer'
|
||||
- 'technical writer roadmap'
|
||||
- 'technical writer'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Enum
|
||||
|
||||
Enums is not a type-level extension of JavaScript. It allow a developer to define a set of named constants. Using enums can make it easier to document intent, or create a set of distinct cases. TypeScript provides both numeric and string-based enums.
|
||||
Enums is not a type-level extension of JavaScript. It allows a developer to define a set of named constants. Using enums can make it easier to document intent, or create a set of distinct cases. TypeScript provides both numeric and string-based enums.
|
||||
|
||||
Here is an example of a numeric enum in TypeScript:
|
||||
|
||||
|
||||
@@ -1,16 +1,18 @@
|
||||
# As Type
|
||||
|
||||
as is a type assertion in TypeScript that allows you to tell the compiler to treat a value as a specific type, regardless of its inferred type.
|
||||
|
||||
For example:
|
||||
In TypeScript, the as keyword is used for type assertions, allowing you to explicitly inform the compiler about the type of a value when it cannot be inferred automatically. Type assertions are a way to override the default static type-checking behavior and tell the compiler that you know more about the type of a particular expression than it does.
|
||||
|
||||
Here's a simple example:
|
||||
|
||||
```typescript
|
||||
let num = 42;
|
||||
let str = num as string;
|
||||
let someValue: any = "Hello, TypeScript!";
|
||||
let strLength: number = (someValue as string).length;
|
||||
|
||||
// str is now of type string, even though num is a number
|
||||
console.log(strLength); // Outputs: 20
|
||||
```
|
||||
In this example, someValue is initially of type any, and we use the as operator to assert that it is of type string before accessing its length property. It's important to note that type assertions do not change the underlying runtime representation; they are a compile-time construct used for static type checking in TypeScript.
|
||||
|
||||
It's important to note that type assertions do not change the runtime type of a value, and do not cause any type of conversion. They simply provide a way for the programmer to override the type inference performed by the compiler.
|
||||
|
||||
- [Type assertions](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#type-assertions)
|
||||
- [Type assertions](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#type-assertions)
|
||||
|
||||
@@ -3,9 +3,9 @@ jsonUrl: '/jsons/roadmaps/typescript.json'
|
||||
pdfUrl: '/pdfs/roadmaps/typescript.pdf'
|
||||
order: 6
|
||||
briefTitle: 'TypeScript'
|
||||
briefDescription: 'Everything you need to learn about TypeScript in 2023'
|
||||
briefDescription: 'Everything you need to learn about TypeScript in 2024'
|
||||
title: 'TypeScript'
|
||||
description: 'Everything you need to learn about TypeScript in 2023'
|
||||
description: 'Everything you need to learn about TypeScript in 2024'
|
||||
hasTopics: true
|
||||
isNew: false
|
||||
dimensions:
|
||||
@@ -13,7 +13,7 @@ dimensions:
|
||||
height: 1884.38
|
||||
schema:
|
||||
headline: 'TypeScript Roadmap'
|
||||
description: 'Learn everything about TypeScript with this interactive step by step guide in 2023. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
description: 'Learn everything about TypeScript with this interactive step by step guide in 2024. We also have resources and short descriptions attached to the roadmap items so you can get everything you want to learn in one place.'
|
||||
imageUrl: 'https://roadmap.sh/roadmaps/typescript.png'
|
||||
datePublished: '2023-01-05'
|
||||
dateModified: '2023-01-20'
|
||||
@@ -21,8 +21,8 @@ seo:
|
||||
title: 'TypeScript Roadmap: Learn to become a TypeScript developer'
|
||||
description: 'Community driven, articles, resources, guides, interview questions, quizzes for typescript development. Learn to become a modern TypeScript developer by following the steps, skills, resources and guides listed in this roadmap.'
|
||||
keywords:
|
||||
- 'typescript roadmap 2023'
|
||||
- 'typescript developer roadmap 2023'
|
||||
- 'typescript roadmap 2024'
|
||||
- 'typescript developer roadmap 2024'
|
||||
- 'guide to becoming a typescript developer'
|
||||
- 'guide to learning typescript'
|
||||
- 'typescript developer roadmap'
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user