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

derby-standalone-builder

v0.1.1

Published

Build Derby-standalone app from regular Derby.js app

Downloads

8

Readme

derby-standalone-builder

Build Derby-standalone app from regular Derby.js app

The result you get is a single file with your Derby app that can be run offline and hosted on a static website hosting providers like GitHub Pages

Usage

builder.build(app, publicPath, outPath, initBundle, cb)

outPath by default is publicPath + '/derby/index.html'

Simplest example:

// build.js

var app = require('./src/app');
var builder = require('derby-standalone-builder')

builder.build(app, __dirname);

Run with node build.js and open the generated ./derby/index.html file directly in your browser to check that it's working offline.

Example with more options and a test server running to quickly test build.

# build.coffee

# Require your regular Derby.js app
app = require './src/app'

builder = require 'derby-standalone-builder'
path = require 'path'

publicPath = path.normalize(__dirname + '/public') 

builder.build app, publicPath, null
, (browserify) ->
  # Put here some additional scripts to include into bundle 
  # or expose via browserify.require  

  # I.e. jQuery installed via Bower:
  browserify.add path.join publicPath, 'vendor/jquery/dist/jquery.js'  
  
, (outPath) ->  
  console.log 'Derby-standalone build created: ' + outPath
  builder.runTestServer(publicPath)

Run

coffee build.coffee

This will genenate a Derby-standalone app from your regular Derby.js app and run a simple server on localhost:3000 which serves the result of the build -- single static index.html file.

licence

MIT