danielsan

const createAPromise = s => new Promise((resolve) => {
  console.log(`this promise will resolve in ${s} seconds`);
  setTimeout(() => {
    resolve(s);
    console.log(`promise solved after ${s} seconds`);
  }, s * 1000);
});

const promises = [];

mohsen1

[
  {
  "key": "shift+cmd+d",
  "command": "editor.action.copyLinesDownAction"
  },

  {
  "key": "cmd+l",
  "command": "expandLineSelection"
  },

rafszul

AniJS ScrollReveal Quick Start

A Pen by Dariel Noel Vila Plagado on CodePen.

License.

zenorocha

Project Name

TODO: Write a project description

Installation

TODO: Describe the installation process

Usage

0xjjpa

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job