NodeJS Ecosystem - Revision history

Rasimsen: /* NestJs */

2019-07-31T09:49:04Z

‎NestJs

Rasimsen at 13:38, 30 July 2019

2019-07-30T13:38:50Z

Rasimsen at 13:25, 30 July 2019

2019-07-30T13:25:07Z

Rasimsen at 10:16, 16 July 2019

2019-07-16T10:16:02Z

Rasimsen at 10:15, 16 July 2019

2019-07-16T10:15:25Z

Rasimsen at 18:08, 6 February 2019

2019-02-06T18:08:14Z

Rasimsen at 17:46, 16 January 2019

2019-01-16T17:46:02Z

Rasimsen at 22:00, 15 January 2019

2019-01-15T22:00:44Z

Rasimsen: Created page with "=NPM= =BootStrap= =JQuery= =TypeScript= =Node.js= =Expres= =NestJs= =GraphQL= ==Apollo GraphQL== =MongoDb= =DynamoDb="

2019-01-15T11:48:18Z

Created page with "=NPM= =BootStrap= =JQuery= =TypeScript= =Node.js= =Expres= =NestJs= =GraphQL= ==Apollo GraphQL== =MongoDb= =DynamoDb="

New page

=[[NPM]]=
=[[BootStrap]]=
=[[JQuery]]=
=[[TypeScript]]=
=[[Node.js]]=
=[[Expres]]=
=[[NestJs]]=
=[[GraphQL]]=
==[[Apollo GraphQL]]==
=[[MongoDb]]=
=[[DynamoDb]]=

@@ Line 9: / Line 9: @@
   * https://docs.nestjs.com/techniques/security
   * https://helmetjs.github.io/docs/
 == [[Security]]==
 == [[Helmet]] - Security/NoCache==

@@ Line 7: / Line 7: @@
 =[[Expres]]=
 =[[NestJs]]=
 =[[GraphQL]]=
 =[[TypeOrm]]=
@@ Line 13: / Line 18: @@
 =[[DynamoDb]]=
 =[[Visual Studio Code]]=
 =Best Practises=

← Older revision		Revision as of 13:25, 30 July 2019
Line 14:		Line 14:
	=[[Visual Studio Code]]=		=[[Visual Studio Code]]=

−		+	=Best Practises=
		+	* https://expressjs.com/en/advanced/best-practice-security.html

← Older revision		Revision as of 10:15, 16 July 2019
Line 12:		Line 12:
	=[[DynamoDb]]=		=[[DynamoDb]]=
	=[[Visual Studio Code]]=		=[[Visual Studio Code]]=
		+	=[[Node.js Project Structure]]=

← Older revision		Revision as of 17:46, 16 January 2019
Line 11:		Line 11:
	=[[DynamoDb]]=		=[[DynamoDb]]=
	=[[Visual Studio Code]]=		=[[Visual Studio Code]]=
		+
		+
		+
		+	=Others=
		+	Async / await keywords are available in TypeScript since 1.7 version. Until new realease, they were transpiled to generator functions using yield. In 2.1, async and wait are finally downleveling to ES3 and ES5, so now, we could use those features in compatibility with browsers.
		+
		+	==Callback Hell==
		+	JavaScript is an incredible powerful language. Through its events loop and non-blocking I/O nature, we could easily build asynchronous applications. In the past, to achieve events-based structure, we were using callbacks. Sometimes our code looks like below:
		+
		+	<syntaxhighlight lang="JavaScript">
		+	setTimeout(function() {
		+	console.log('First');
		+	setTimeout(function() {
		+	console.log('Second');
		+	setTimeout(function() {
		+	console.log('Third');
		+	setTimeout(function() {
		+	console.log('Fourth');
		+	}, 500);
		+	}, 1000);
		+	}, 500);
		+	}, 1000);
		+	</syntaxhighlight>
		+	It is a callback hell. Probably, if our code would be more complex, trying to understand it for another person will looks like this:
		+	https://kamilmysliwiec.com/wp-content/uploads/2016/12/cat-gif.gif
		+
		+	It wasn’t a good solution. They are a lot of ways to deal with it. The most common are Promises.
		+
		+	==What is Promise?==
		+
		+	Promise is just an object that represents a task. It might finish right now or in a little while. We could interact with „task” by passing a callback to its then function. Let’s rewrite our previous example using Promises and arrow functions.
		+
		+	<syntaxhighlight lang="JavaScript">
		+	const resolver = (msg, timeout) => new Promise((resolve) => {
		+	console.log(msg);
		+	setTimeout(resolve, timeout);
		+	});
		+	resolver('First', 500)
		+	.then(() => resolver('Second', 500))
		+	.then(() => resolver('Third', 1000))
		+	.then(() => resolver('Fourth', 500));
		+	</syntaxhighlight>
		+
		+	Looks simplier – same result.
		+
		+	==Async / await==
		+	Async and await keywords are well-known in C# community. They allows us to write asynchronous code in more synchronous way. Let’s rewrite our example again using those features.
		+
		+	<syntaxhighlight lang="JavaScript">
		+	const resolver = (msg, timeout) => new Promise((resolve) => {
		+	console.log(msg);
		+	setTimeout(resolve, timeout);
		+	});
		+	async function run() {
		+	await resolver('First', 1000);
		+	await resolver('Second', 500);
		+	await resolver('Third', 1000);
		+	await resolver('Fourth', 500);
		+	}
		+	run();
		+	</syntaxhighlight>
		+
		+	It also do the same stuff. '''The simplest explanation of how it works is that await takes a Promise and waits until task is finished. If method has at least one await keyword, it has to have async keyword before function declaration.''' That’s all.
		+
		+	resource: https://kamilmysliwiec.com/typescript-2-1-introduction-async-await
		+
		+
		+
		+
		+	<syntaxhighlight lang="JavaScript">
		+
		+	</syntaxhighlight>
		+
		+	<syntaxhighlight lang="JavaScript">
		+
		+	</syntaxhighlight>
		+
		+	<syntaxhighlight lang="JavaScript">
		+
		+	</syntaxhighlight>
		+
		+	<syntaxhighlight lang="JavaScript">
		+
		+	</syntaxhighlight>

@@ Line 1: / Line 1: @@
 =[[NPM]]=
 =[[BootStrap]]=
 =[[JQuery]]=
@@ Line 12: / Line 13: @@
 =[[DynamoDb]]=
 =[[Visual Studio Code]]=
-=[[Node.js Project Structure]]=

← Older revision		Revision as of 22:00, 15 January 2019
Line 10:		Line 10:
	=[[MongoDb]]=		=[[MongoDb]]=
	=[[DynamoDb]]=		=[[DynamoDb]]=
		+	=[[Visual Studio Code]]=