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

nanoconstruct

v0.3.0

Published

Tiny tool to test and develop nanocomponents

Downloads

10

Readme

nanoconstruct

Tiny tool to test and develop nanocomponents.

nanoconstruct provides a very simple wrapper around your components and serves them on a simple interface you can access with your browser. It's inspired by Kit and uses budo under the hood.

It includes choo-devtools, so you have access to the state and other Choo things, and tape for testing.

Demo of nanoconstruct

Installation

npm i nanoconstruct

Usage

If your component depends on a custom state or parameters, you can wrap it into a simple wrapper function. Otherwise, a neutral wrapper will be used around the component.

A simple wrapper function looks like this:

var html = require('choo/html')
var Component = require('./components/component')

var c = new Component()

module.exports = () => html`${c.render()}`

Then just point nanoconstruct to the file with:

nanoconstruct example.js

Tests

I want nanoconstruct to provide you with everything you might need to work on a component. So why not tests? You can define a test(t, el) function in your exported wrapper and it'll be ran automatically when you select the component in the app. Check the console!

It gets a tape test object and the rendered element.

var html = require('choo/html')
var Alert = require('./components/alert')

var component = new Alert('Click me!')

module.exports = {
  render: () => html`
    ${component.render(':)')}
  `,
  test: (t, el) => {
    t.plan(1)
    t.equal(el.innerHTML, 'Click me!')
  }
}

Multiple Components

It's also possible to use your whole component library at once. Use the --library mode and point nanoconstruct to a directory of wrapper functions or components.

However, if the structure of your components isn't that simple, export all the wrappers or components from a .js file and use this as input.

Like this:

module.exports = {
  Title: require('./title-wrapper'),
  Content: require('./component/content')
}

CLI

usage
  nanoconstruct [opts] <entry>
options
  --help, -h              show this help text
  --library, -l           use all the files from a library
  --open, -o              open the page in the browser
  --port, -p              server port
  --version, -v           print version
examples
  start server
  nanoconstruct example.js

  start server on port 3000 and open it
  nanoconstruct example.js -p 3000 -o

  start server with library mode
  nanoconstruct components --library