ankit-kumar-jat

How to resolve package-lock.json conflicts

It is not possible to resolve conflicts of package-lock.json in GitHub's merge tool and you need to do a manual merge.

1. Update the master branch with the latest changes:

   git checkout master
   git pull
   

2. Merge your feature branch into master:

ankit-kumar-jat

Sass Architecture Structure

sass/
|
|– base/
|   |– _reset.scss       # Reset/normalize
|   |– _typography.scss  # Typography rules
|   ...                  # Etc…
|

ankit-kumar-jat

 /**
  *
  * @param {String} url scrip url
  * @param {String} id id for script tag
  * @returns promise
  */
 const loadScript = (url, id) => {
   return new Promise((resolve) => {
     const existingScript = document.getElementById(id);
     if (existingScript) resolve(true);

ankit-kumar-jat

import axios from 'axios'

export const axiosBaseQuery =
  ({ baseUrl, prepareHeaders }) => {
    return async ({ url, method, body: data, params, ...rest }, api) => {

      try {
        // this to allow prepare headers 
        if (prepareHeaders) {
          axios.interceptors.request.use(function (config) {

ankit-kumar-jat

ACL / Roles + Permissions

https://github.com/djvirgen/virgen-acl Simple and elegant, create your own checks. No middleware?

https://github.com/OptimalBits/node_acl Use as middleware, create your own roles and access. Great choice.

https://github.com/tschaub/authorized Similar to connect roles... but a bit more robust? you can create roles and action, and associate many roles with that action

ankit-kumar-jat

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

ankit-kumar-jat

const version = 1;
const cacheName = `our_awesome_cache`

// the static files we want to cache
const staticFiles = [
  'index.html',
  'src/css/styles.css',
  'src/img/logo.png',
  'src/js/app.js'
];