npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@dot-event/view

v0.0.34

Published

dot-event views

Downloads

36

Readme

@dot-event/view

dot-event dom views

view

Install

npm install dot-event @dot-event/view

Setup

const dot = require("dot-event")()
require("@dot-event/view")(dot)

Usage

First create your view composer:

module.exports = function(dot) {
  dot.view("myView", { render, update })
}

function render() {
  return document.createElement("DIV")
}

function update(prop, arg) {
  arg.element.innerHTML = arg.value
}

Then use it:

require("./myView")(dot)

dot.myView() // `render` element
dot.myView({ value: "hello" }) // `update` element

Attach to dom

By default, the view call finds the element id from props:

dot.myView("myId") // `render` element to #myId
dot.myView("myId") // `update` element if element returned

You may also specify a selector:

dot.myView({ selector: "#myId" }) // `render` element to #myId

Or provide the element to replace directly:

dot.myView({ element: document.getElementById("myId") })

SSR

If an element already exists and has content, the update function is called instead of the inital render.

The emit argument to the update function includes an ssr: true option when in SSR mode.

Props

Commonly we append the view name to the prop array and pass the concatenated props to sub-events.

Passing those props down produces descriptive element ids and logs that describe the call stack.

Luckily, the view composer injects the view name into the prop array automatically, eliminating the view name append step.

Related composers

| Library | Description | URL | | ---------- | ------------------ | ---------------------------------------------- | | controller | DOM controller | https://github.com/dot-event/controller#readme | | el | DOM elements | https://github.com/dot-event/el#readme | | render | Server side render | https://github.com/dot-event/render#readme |