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

jallaify

v1.1.2

Published

Browserify plugin for bundling applications built with jalla

Downloads

9

Readme

jallaify 💫

npm version build status downloads style

Browserify plugin for bundling entire choo applications built with jalla, front- and back-end, into a single file. Especially usefull with serverless platforms, e.g. Zeit, AWS etc.

Usage

If you're just using the jalla CLI you'll have to create a server entry file. The equivalent of running jalla index.js would be to create a file as such:

// server.js
var jalla = require('jalla')
var app = jalla('index.js')
module.exports = app.callback()

If you already have a server file you will probably need to make some small changes. Since most serverless platforms expect a single function export, calling server.listen() will not work. E.g. [@now/node][@node/now] expects a function which takes req and res. To comply with Now, you would export app.callback() which will return a function accepting req and res.

// server.js
var jalla = require('jalla')
var app = jalla('index.js')

if (process.env.IS_SERVERLESS) module.exports = app.callback()
else app.listen(8080)

Provide the server entry file to browserify and define jallaify as a plugin.

$ browserify index.js --node --standalone my-app -p jallaify > build.js

Any options provided to jallaify will be forwarded to the compiled jalla app.

$ browserify index.js --node --standalone my-app -p [ jallaify --sw sw.js ] > build.js

The standalone option is required for browserify to actually expose the application export and not just execute the bundled code.

The bundled application is intended to run in production mode (not watching for changes) and serving built assets. Jallaify will make a best effort to infer the serve option but it is good practice to explicitly define it.

var jalla = require('jalla')
var app = jalla('index.js', {
  serve: Boolean(process.env.IS_SERVERLESS)
})

if (process.env.IS_SERVERLESS) module.exports = app.callback()
else app.listen(8080)

See Also

License

MIT