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

generator-cljs-fullstack

v0.1.0-alpha.1

Published

Yeoman generator for webapps utilizing ClojureScript on the front-end and back-end.

Downloads

10

Readme

Cljs Full Stack

Yeoman generator for building web applications leveraging ClojureScript on both the front-end and back-end.

Features:

  • Livereload of client and server files
  • Easy distribution generation
  • Stack traces with source maps applied in Node.js
  • Support for testing using Specljs
  • Support for Sass and Compass

Requirements

Usage

First, install the generator:

npm install -g generator-cljs-fullstack

If you want to do development on the generator itself, do this instead:

git clone https://github.com/johntrimble/generator-cljs-fullstack.git
cd generator-cljs-fullstack
npm install
npm link

Then create a new project by executing the following:

mkdir my-project
cd my-project
yo cljs-fullstack <app-name>

Development

From the project root, execute the following:

grunt serve

This will:

  • Compile ClojureScript source
  • Compile Sass source
  • Start a node server running backend code at http://localhost:4000
  • Start a static content server at http://localhost:9000
    • Proxies http://localhost:9000/api/ to http://localhost:4000/api/
    • Live reloads the browser on content changes (updating ClojureScript code, HTML, CSS, etc.)

Assuming there are no errors, this task should automagically open up a browser window to http://localhost:9000.

If you'd like to have your tests run continuously in the background as well, use the --with-tests options:

grunt serve --with-tests

Distribution

From the project root, execute the following:

grunt

This will:

  • Compile ClojureScript server source
  • Compile ClojureScript client source with advanced mode
  • Compile Sass source
  • Concatenate and minify JavaScript source
  • Minify HTML source
  • Put all backend assets under dist
  • Put all frontend assets under the dist/public directory
  • Generate a suitable package.json at dist/package.json

Assuming there are no errors, the dist directory will be a self contained distribution of the application. The application can be started by running the following:

cd dist
npm install
npm start

Testing

From the project root, execute the following:

grunt test

This will:

  • Compile ClojureScript source for the backend and frontend
  • Run the backend and frontend tests

Note: This effectively runs lein cljsbuild once twice, once for the backend and once for the frontend. This means it's slow. If you plan on running tests continuously, you may want to look at running in develop