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

edon-http

v0.0.2

Published

A Route-less Node HTTP Server - the simplest way possible.

Downloads

4

Readme

edon-http

A Route-less Node HTTP Server - the simplest way possible. Old-school is so cool...

Route-less structure:

Two key directories: '/private/' and '/public/'.

	'/private/'
		Server-side Nodejs files go here
		in whatever vanilla, MVC, clean
		or crazy directory structure you want.
		Example: a url of 'htp://site.com/login'
		will hit the nodejs file '/private/login.js'
		Nothing inside the /private/ directory
		can be accessed accidentally like a
		client-side .js file. Your source is safe.

	'/public/'
		Client-side files go here, like:
		/public/scripts/jquery.min.js
		/public/styles/global-styles.css
		/public/images/cat.gif.
		These will use their /public/ base,
		meaning: <link type="text/css" rel="stylesheet" href="/public/styles/global-styles.css">

	Your default landing page when nothing is specified in the URL, ie. 'http://site.com/' will hit 'private/index.js'.

A basic node http server start file:

Here is a sample server.js file which you would start by running "node server".
In this example below you can specify the port to listen on "node server 8080" or "sudo node server 80".

------------------------------------------------------------------------------------
// File: server.js
// Created: January 2016

var Edon = require("./edon-http.js"),
	Http = require("http");

// Make 'Edon' accessible EVERYWHERE
global.edon = new Edon();

var svr = Http.createServer(global.edon.listener),
	port = 8888;

console.log(process.argv);
if (process.argv.length > 2 && !isNaN(process.argv[2]) && process.argv[2] >= 80) {
	port = process.argv[2];
}

svr.listen(port);

console.log("Edon Server is running!\n\nListening on port: " + port + ".\n\n\n")
------------------------------------------------------------------------------------

There are additional functions in edon-http for static file usage:

Referencing 'global.edon = new Edon();' from the sample 'server.js' shown above:

INC - to include static file content:
	response.write(global.edon.inc("./views/login_form.html"));

REQR - to include nodejs file functions
	self.reqr(path.resolve(global.edon.serverDir + "error/404notfound.js"));  // self.serverDir = '/private/'

QS2OBJ
	request.reqUrlParams = global.edon.qs2obj(request.reqUrl.query);