Skip to content
Tool set for generating web components based web project.
JavaScript HTML
Branch: master
Clone or download
Latest commit d0ef97b Jan 20, 2020
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
commands Update. Jan 19, 2020
lib Prevent duplicated bind. Jan 20, 2020
templates Update. Jan 19, 2020
.gitignore Added tokenizer for component2. Jan 2, 2020
LICENSE Updated third party licenses and credits. Jan 14, 2020
README.md Updated third party licenses and credits. Jan 14, 2020
leanweb.js Update. Jan 14, 2020
package.json Added component2 template. Jan 14, 2020

README.md

leanweb

Tool set for generating web components based web project.

Installation

  • npm install leanweb -g as a global tool, or
  • npm install leanweb -D in the project as a dev dependency.

If leanweb is installed as a dev dependency of the project, you will need to run npx leanweb, otherwise just run leanweb if it is installed as global tool.

I don't see any reason leanweb should be installed as npm install leanweb.

Background

I like the idea in Angular that 3 files (html/js/scss) as a component are in charge of a box, like a div, a rectangle area. But I don't like Angular in that my code has to be depending on so many bloated dependencies to run. I created leanweb as a set of tools to help me create web components based web projects, which:

  • come with zero dependency
  • are based on native web components api
  • are built to last

The principle is simply that 3 files (html/js/scss) as a web component will control a box.

Getting started

In this demo, I assume leanweb is installed as a global tool by running

npm i leanweb -g

leanweb init

Create a directory called demo for this demo project.

$ mkdir demo
$ cd demo
demo$ leanweb init
demo$

Now a leanweb.json file and a src/ directory are created at the project root. leanweb.json looks like:

{
  "name": "demo",
  "title": "demo",
  "components": [
    "demo-root"
  ]
}

which suggests a root web component demo-root is created by leanweb init. In src/ directory, an empty demo.scss file is created, in which we can add global styling scss code. demo-root web component directory is created at src/components/demo-root/. There are 3 files in this directory:

  • demo-root.html
  • demo-root.js
  • demo-root.scss

demo-root.html

<span>root works</span>

demo-root.js

customElements.define('demo-root',
  class extends HTMLElement {
    constructor() {
      super();

      const templateNode = document.querySelector('#demo-root').content.cloneNode(true);
      // attach to shadow dom
      this.attachShadow({ mode: 'open' }).appendChild(templateNode);
      // attach to normal dom
      // this.appendChild(templateNode);
    }

    // connectedCallback() {
    //   console.log(this.isConnected);
    //   console.log('Element added to page.');
    // }

    // disconnectedCallback() {
    //   console.log('Element removed from page.');
    // }

    // adoptedCallback() {
    //   console.log('Element moved to new page.');
    // }

    // static get observedAttributes() {
    //   return [];
    // }

    // attributeChangedCallback(name, oldValue, newValue) {
    //   console.log(name, oldValue, newValue);
    // }
  }
);

demo-root.scss is empty.

Now if you run leanweb dist or leanweb di, a dist/ directory will be created. There will be 3 files inside:

  • index.html
  • demo.js
  • demo.css

If you deploy these 3 files to a web server, you should see root works in browser.

leanweb generate

Let's create a login web component with leanweb generate or leanweb g.

demo$ leanweb g login
demo$

Now the leanweb.json has one more entry in the component list:

{
  "name": "demo",
  "title": "demo",
  "components": [
    "demo-root",
    "demo-login"
  ]
}

demo-login is the newly generated web component. The web component name is prefixed with project name demo. Inside src/components/, a new web component directory demo-login is created containing 3 files:

  • demo-login.html
  • demo-login.js
  • demo-login.scss

leanweb build

Let's open src/components/demo-root/demo-root.html, which previously looks like:

<span>root works</span>

Now let's add one line to this file:

<span>root works</span>
<demo-login></demo-login>

then run:

demo$ leanweb build

You should see root works login works in the browser.

leanweb dist

Unlike leanweb build, leanweb dist will combine all js files into one demo.js. index.html, demo.js and demo.css will be created in the dist/ directory.

leanweb clean

leanweb clean will delete build/ and dist/ directories.

leanweb destroy

leanweb destrory project-name will remove the leanweb.json file, src/, build/ and dist/ directory. Please note the src/ directory will be deleted by this command.

leanweb help

leanweb help command-name will print help information for the command. For example, leanweb help dist or leanweb h di will print:

demo$ npx leanweb h di
Usage: leanweb dist
This will create a dist directory in which 3 files will be created:

index.html
demo.js
demo.css

These 3 files could be deployed to a web server.

demo$

leanweb version

leanweb version will print the version information of leanweb.

Credits

You can’t perform that action at this time.