lxynox

When you create a npm package, remember it might be used in a browser or a server, or even a command line utility… For each package you create, please pay attention at what it will be used for:

1. Is it going to be used as a dependency to a nodejs application that is not bundled? (e.g. command line utilities)
2. Is it going to be used as a dependency to a nodejs application that is bundled? (e.g. AWS Lambdas)
3. Is it going to be used as a dependency to a browser application (always bundled)?.

• In cases 2) and 3) you want to allow for tree shaking.
• In cases 1) and 2) you want to benefit from the "ES6"/"ES next" features supported natively by nodejs.
• In case 3) you also want to benefit from the native support of "ES6" from your browser.

lxynox

asycn/await

async function readFiles(files) {
  for(const file of files) {
    await readFile(file);
  }
};

yield

lxynox

Always starts from changing node_modules/ directly, for more complex use cases

🔰🔰🔰

npm link

/path/to/lib $ npm link
/path/to/app $ npm link lib

lxynox

Mobx-State-Tree (MST)

mobx-state-tree is a state container that combines the simplicity and ease of mutable data with the traceability of immutable data and the reactiveness and performance of observable data.

How???

feature/
  state/
 - index.js

lxynox

Why statelessness

visibility

Every request contains all context necessary to understand it. Therefore, looking at a single request is sufficient to visualize the interaction.

reliability

Since a request stands on its own, failure of one request does not influence others.

lxynox

Proxy

First of all, the word "proxy" describes someone or something acting on behalf of someone else.

In the computer realm, we are talking about one server acting on the behalf of another computer.

Forward proxy

Acting on behalf of client (browser)

lxynox

WebSockets - An Introduction

WebSockets is a modern HTML5 standard which makes communication between client and server a lot more simpler than ever. We are all familiar with the technology of sockets. Sockets have been fundamental to network communication for a long time but usually the communication over the browser has been restricted. The general restrictions

• The server used to have a permanent listener while the client (aka browser) was not designated any fixed listener for a more long term connection. Hence, every communication was restricted to the client demanding and the server responding.
• This meant that unless the client requested for a particular resource, the server was unable to push such a resource to the client.
• This was detrimental since the client is then forced to check with the server at regular intervals. This meant a lot of libraries focused on optimizing asynchronous calls and identifying the response of asynchronous calls. Notably t

lxynox

Problem

• setState is called on unmounted component
• race conditions among multiple in-flight requests (responses come back out of order)

Solution

Make the promise cancellable

lxynox

Middlewares

api: [app/router].use

Scope/Hierarchy of middlewares

• Application-level middleware
• Router-level middleware

lxynox

package.json

"files" vs .npmignore

files - whitelisting all files that should be included in a npm release

.npmignore - blacklisting all files that should be included in a npm release

package-lock.json