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

flexbuilder

v0.0.0

Published

A generic builder

Downloads

13

Readme

FlexBuilder

  • A module bundler, ESNext builder and development tool, using webpack, babel and nodemon

Installation

yarn add --dev flexbuilder or npm install --dev flexbuilder

Install all necessary peer dependencies. Except react and react-dom, the rest should be installed as dev dependencies.

Usage

Add a build.js file at the root

build.js

process.on('unhandledRejection', (reason, p) => { throw reason });

require('babel-polyfill');
const builder = require('flexbuilder').default;
const argv = require('yargs').argv;

builder({
	root: __dirname,
	dev: !!argv.dev,
	// options documented below
});

Add these scripts to the package.json file:

package.json

{
	"scripts": {
		"dev": "node ./build --dev",
		"build": "node ./build"
	}
}

If you have symlinked modules in your project (only during development), add node's --preserve-symlinks flag to the commands above.

package.json (for symlinked modules)

{
	"scripts": {
		"dev": "node --preserve-symlinks ./build --dev",
		"build": "node --preserve-symlinks ./build"
	}
}

Options

| Name | Required | Description | | --------------|:---------:| -----:| | root | Yes | Root of the project. Use __dirname | | dev | Yes | Should run in dev mode? It's best to use !!argv.dev | | start | Yes if target is an app and server code needs to be run in dev mode | relative path to the distribution server file | | library | Yes if target is a library | Name of the library | | sources | Yes | { server: {}, client: {} } Each key in the server or client object is used as the destination file name. Each value is a relative path to the source directory | | alias | No | { server: {}, client: {} } Aliases to be used to resolve modules on the server and/or client. It's best to use require.resolve instead of an absolute path here. | | define | No | { server: {}, client: {} } Use to define any extra compile-time variables. | | devServerPort | Yes if using webpack dev server | You must explicitly provide a port for webpack dev server |