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

@lespantsfancy/lux

v0.3.45

Published

Adds some functionality to stuff to be used in ways consistent with that added functionality

Downloads

56

Readme

Setup

All files should be placed in the /src/ directory. Upon running the npm run prepublish command (either directly or indirectly), any files and folders under /src/ will be sent through babel to the /lib/ directory. The package.json file specifies the entry point of the package to the /lib/index.js point. /lib/index.js will be a babel copy of /src/index.js.

Project Structure

Directory

lux [root]
  └─ /lib   [dynamically copied from /src]
  └─ /src
    └─ /core
    └─ index.js

Namespace

import Lux from "@lespantsfancy/lux";

Gives access to the following namespaces:

Lux
  └─ Core
    └─ ...

Purpose of Babel

As of the time of this package, I don't know enough about how this (Node, packages, etc.) works and babel ensured (tested and verified) that es6 files and structure would compile and be available both in a NodeJS level execution (i.e. an express sever) and in a React application.

At this point, it has not been tested with React Native.

Installation

npm install @lespantsfancy/lux

Because this is a scoped package, you must install it with the @lespantsfancy prefix. |Scope|Command| |---|---| |Production|npm install --save @lespantsfancy/lux| |Development|npm install --save-dev @lespantsfancy/lux|

Example Usage

import Lux from "@lespantsfancy/lux";

NPM

These are all cli level commands and require a terminal to execute.

NPM Login

npm login

Follow the prompts to login with username, password, and email.

NPM Packaging Commands

npm version patch|minor|major

This will increment the version of the package

npm publish --access=public

This will deploy the package to npm

Commands

Development Commands

npm start

This is a custom script that will run the prepublish command before executing node lib/index.js

Command Execution Steps

1) `npm run prepublish`
2) `cls`
3) `node lib/index.js`

Publishing Commands

npm run deploy

This is a custom script to both increment the patch and publish to npm.

Command Execution Steps

1) `npm version patch`
2) `npm publish --access=public`
   a) `babel` apparently knows to `npm run prepublish` behind the scenes here