Skip to content
/ breeze Public

A front-end framework for working with Web Components, aiming to make the process of crafting Web Components easier, faster and more pleasant.

License

Notifications You must be signed in to change notification settings

zeemeng/breeze

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Breeze

NPM package version supported node version minified bundle size license

About

Breeze is a framework for working with Web Components. It aims to make the process of crafting Web Components easier, faster and more pleasant. It requires no build step, has no dependency, and is quick to get started with.

Installation

Via NPM:

$ npm i breeze-wc

or git clone this repository.

Usage

The following guide assumes that the reader has a basic understanding of Web Components. If such is not the case, it is recommended to first check out the resources listed in the learn more section below.

Import and setup:

First add a script tag of type "module" pointing to the location/url where your component definition will be found.

<!-- FILE index.html -->
<head>
  ...
  <script type="module" src="./MyComponent.js">
</head>

Then import Component from Breeze and export a custom class definition extending Component.

/* FILE MyComponent.js */
import Component from "breeze-wc"; // In a Node environment (will require a module bundler/build step)

// OR

import Component from "./breeze/index.js"; // Import from index.js in non-Node environments (DOES NOT require a build step)

export class MyComponent extends Component {}

Note that importing from Breeze using a NPM package specifier will require a bundler tool such as Webpack or Rollup to process your files since browsers cannot work with such specifier format. Though if you installed via NPM, you can still avoid the need to use a bundler tool by importing directly from node_modules/breeze-wc/index.js.

Basic component example

import Component from "./breeze/index.js";

export class MyComponent extends Component {
  static tagName = "my-component";

  static template = `
  <div>Hello world!</div>
  <p>Good morning!</p>
  `;

  static styleSheet = `
  div {
    color: blue;
  }

  p {
    font-weight: 700;
  }
  `;

  static init = this.initClass();
}

This will define a custom HTML element that uses the tag <my-component></my-component> in the main HTML document. The template static property defines the contents of the custom element's shadow DOM. The StyleSheet static property will create a <style></style> in the shadow DOM that has the the given string value as it's content. Finally it is very important to call MyComponent.initClass(), since it is this method that initializes the custom element according to the definition that we provide. In the above example, the method is invoked in the declaration static init = this.initClass(). The static property init itself is of no importance, we only use it for convenience reasons.

Advanced component example

import Component from "./breeze/index.js";

export class MyComponent extends Component {
  static tagName = "my-component";

  static template = `
  <div>Hello world!</div>
  <p>Good morning!</p>
  <div class="counter"></div>
  `;

  static styleSheetPaths = "./a-path/to-a-css-file.css"; // A path or an array of paths to a CSS file relative to the HTML document. These files shall contain rulesets that apply to the shadow DOM tree of the custom element.

  static init = this.initClass();

  counterState = this.createState(0); // Creates a local state value and assign it to a public class property.

  // Lifecycle method defined by the "WHATWG HTML Spec".
  connectedCallback() {
    setInterval(() => this.counterState.mutate(this.counterState.value + 1), 1000); // Increments the state value every 1000ms.
  }

  // Special method invoke on every local state mutation.
  render() {
    this.shadowRoot.querySelector(".counter").textContent = this.counterState.value;
  }
}

Note that as observed in the above example, render is special method responsible for updating the custom element, the user interface, and for performing other side effects. It is invoked by multiple triggers, such as when the custom element is connected to the DOM tree, when the custom element is upgraded, when states are mutated, and when observed attributes are changed.

Learn more about Web Components

Notes

  • This package is fully annotated and supports IntelliSense.
  • Suggestions and contributions are welcome.

About

A front-end framework for working with Web Components, aiming to make the process of crafting Web Components easier, faster and more pleasant.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published