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

frontend

v2.0.0-alpha.4

Published

A management system for UI/UX Developers.

Downloads

1,216

Readme

frontend

A boilerplate for UI/UX Developers.

Getting Started

There are several ways to use Frontend. Examples can be found at Github.

Step One

A JSON configuration file is used to define the paths for files in order to compile them. The JSON schema should be similar to the example below.

Create a JSON configuration file in the root directory of your project.

$ touch config.json

config.json:

{
  "ts":   { "dest": "dist/dev/js", "src": "src/ts/*.ts" },
  "sass": { "dest": "dist/dev/css", "src": "src/sass/*.scss" },
  "less": { "dest": "dist/dev/css", "src": "src/less/*.less" },
  "html": { "dest": "dist/dev", "templates": "src/html", "mustache": { "base":"src/html/_tmpl/base.mustache" } }
}

NOTE: It is important to use the keys as described since Frontend does not validate against a JSON schema.

Step Two

Create a base Mustache file in the directory defined in the config.json

$ mkdir -p ./src/html/_tmpl && touch ./src/html/_tmpl/base.mustache

base.mustache:

<!DOCTYPE html>
<html lang="en">
<head>
    <title>{{ pageTitle }}</title>
</head>
<body>
    {{> component }}
</body>
</html>
Step Three

Create your first HTML page and corresponding JSON file for data.

$ touch ./src/html/index.html ./src/html/index.json

Every .html file in the templates directory will be parsed as an individual page. The contents of this will be sent through the base template and any partials created. The data comes from a corresponding .json file having the same base name.

index.html:

<h1>{{ heading }}</h1>

How To Build Using Gulp

Use this package to run your Gulp tasks for compiling Sass, Less, Typescript and Mustache files.

Create a new Gulp file in the root directory of your project.

$ touch gulpfile.js

gulpfile.js:

const gulp = require('gulp');
const { build, html, sass, less, ts } = require('frontend');

exports.default = build;
exports["HTML"] = html;
exports["Sass"] = sass;
exports["Less"] = less;
exports["Typescript"] = ts;

List the Gulp tasks that are exported from gulpfile.js

$ gulp --list-tasks

Run a task:

$ gulp default

Go to the Github repo for Mustache to read further information on its usage.