- Postman -
sudo snap install postman
- Atom -
sudo snap install atom --classic
- VSCode -
sudo snap install code --classic
- Android Studio -
sudo snap install android-studio --classic
- Eclipse -
sudo snap install eclipse --classic
/** | |
* @name - JavaScript Interview questions | |
*/ | |
//==== | |
/** | |
* @name - TypeOf | |
* @description - typeof [Number] | |
*/ | |
console.log(typeof 25 === "number"); | |
console.log(typeof 3.14 === "number"); |
#!/bin/sh | |
npm start | while IFS= read -r line; do printf '%s %s\n' "[$(date "+%Y-%m-%d %H:%M:%S")]" "$line"; done >>/log/logger.log |
#!/usr/bin/bash | |
failure() { | |
printf "\n%s\n" "" | |
exit 2 | |
} | |
#*********************************** | |
# CREATE TEMPORARY FOLDER | |
#*********************************** |
function hasEnv(): boolean { | |
try { | |
return Deno.statSync(".env").isFile; | |
} catch (_) { | |
return false; | |
} | |
} | |
async function createEnv(): Promise<void> { | |
const dockerenv = await Deno.open(".env", { |
Initial vscode settings.json
"explorer.confirmDelete": false,
"editor.minimap.enabled": false,
"terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe",
"window.zoomLevel": 1
Libuv has a default thread pool size of 4, and uses a queue to manage access to the thread pool - the upshot is that if you have 5 long-running DB queries all going at the same time, one of them (and any other asynchronous action that relies on the thread pool) will be waiting for those queries to finish before they even get started.
Note, however, that tuning UV_THREADPOOL_SIZE may make more sense for a standalone application like a CLI written in Node.js. If you are standing up a bunch of Node.js processes using the cluster module then I would be surprised if tuning UV_THREADPOOL_SIZE was particularly beneficial for you. But if your application resembles the web tooling benchmarks then tuning UV_THREADPOOL_SIZE may help with performance.
Note: Don't forgot to use
chai.use(require('chai-things'));