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

@deg-skeletor/core

v1.1.1

Published

The core engine for the Skeletor family of build tools

Downloads

50

Readme

Skeletor!

Build Status

Skeletor is a simple task runner for automating common development chores. It has a growing ecosystem of plugins to handle a wide variety of tasks.

Skeletor is built and looked after by the front-end web development team at DEG.

Installation

Skeletor can be installed via npm:

npm install @deg-skeletor/core

Nice job! Next, you'll want to install some plugins.

Plugin Ecosystem

At its core, Skeletor is just a delegator. Plugins do the real work.

A typical Skeeltor plugin does one thing and one thing well. That one thing could be anything. There are plugins for file copying, PostCSS, Pattern Lab, Express, Rollup, and more. Go on, have a look.

Configuration

Skeletor needs a configuration object to tell it what tasks to run and what those tasks are comprised of. A sample configuration object might look like the following:

{
    tasks: [
        {
            /* a task to build all the code in a project */
            name: 'build',
            subTasks: [
                {
                    /* a sub-task to build the CSS code */
                    name: 'css', 
                    plugins: [
                        {
                            /* a plugin to process CSS via PostCSS */
                            name: '@deg-skeletor/plugin-postcss',
                            config: {
                                //Plugin-specific config
                            }
                        }
                    ]
                },
                {
                    /* a sub-task to build static files */
                    name: 'static',
                    plugins: [
                        {
                            /* a plugin to copy static files from one directory to another */
                            name: '@deg-skeletor/plugin-copy',
                            config: {
                                //Plugin-specific config
                            }
                        }
                    ]
                }
            ]
        }
    ]
}

A Skeletor configuration object consists of an array of tasks. A task consists of either plugins or subTasks. A subTask is itself a task with its own plugins or subTasks properties.

By default, Skeletor will look for a configuration file named skeletor.config.js relative to the working directory. Alternatively, a configuration object can be passed directly to Skeletor. See the API section for more details.

CLI

Included within the Skeletor ecosystem is a command line interface for interacting with Skeletor via a terminal. Visit the Skeletor CLI project for more information.

API

Skeletor exposes a compact API for programmatic interaction.

getConfig()

Returns the configuration object.

setConfig()

Sets the configuration object.

setLogger()

Sets the logger for outputting information, warnings, and errors. A simple console logger is used by default.

runTask(taskName, [options])

Runs the specified task.