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

originate-frontend-lib

v0.9.8

Published

loom origin for creating bulletproof javascript libraries with isomorphic packaging

Downloads

18

Readme

originate-frontend-lib

loom origin for creating bulletproof javascript libraries with isomorphic packaging.

This template is based on this project. Refer to it's documentation for details.

Usage

$ npm install -g loom
# now the originate program is available
$ originate frontend-lib my-lib __my-lib-global-name
$ cd my-lib
$ git init
$ npm install
# ready to go!

If you have hub installed, you can streamline your process like that:

originate frontend-lib my-lib __my-lib-global-name
cd my-lib
git init
npm install
npm run build-all && npm run test
git add . && git commit -am "Initial commit"
hub create
git push origin master

Here is a copy-paste oneliner of the previous commands:

git init; npm i; npm run build-all && npm run test; git add . && git commit -am "Initial commit"; hub create; git push origin master

What's inside?

Some really nice stuff is packed:

  • 6to5 transpiles ES6 code into ES5 code. You write your code using new ES6 syntax!

  • All major and new module formats are supported: AMD, CommonJS, ES6 Modules Almost anyone can use your library in browser and NodeJS!

  • Webpack, RequireJS, Browserify, SystemJS compatible! You should not worry how your module will be bundle

  • Can be used in a browser directly: Webpack build configured to produce a standalone UMD version in dist/standalone.js We got those oldschool guys covered as well.

  • Karma + Jasmine test setup (with CI integration for PhantomJS and Firefox!) You can be sure that your code works as intended.

  • Coverage report generated via istanbul If you like numbers, we have added some stuff.

  • npm, jspm and bower support So that your library can be easily distributed.

  • Pre-commit hook with jshint and fixmyjs You cannot commit bad code and break all things.

  • Out-of-box integration with travis, coveralls and bithound Everything is automated! Get those cool badges!

  • Sane defaults for .editorconfig, .npmignore and .gitignore No rubbish get into the repo

Global Name

The 3rd parameter to originate command is the global name of your library. Global name is the string, which is added to the window object, if your library is used as a standalone <script>.