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

gulp-seajs

v0.4.2

Published

seajs builder for gulp

Downloads

13

Readme

gulp-seajs, a seajs builder for gulp

gulp-seajs is a plugin to build seajs modules.

install:

npm install gulp-seajs --save

test

npm test

use:

var seajs = require('gulp-seajs');

gulp.task('seajs build', function(){
    gulp.src('mainfile.js')
    .pipe( seajs('mainID') )
    .pipe( gulp.dest( '/dist' ) );
});

result: /dist/mainfile.js:

define( 'mainID', [ 'model1', 'view1', 'view2', 'util1' ], function(){
    // ... codes here
} );

define( 'model1', ['dependences'], function(){
    // ... codes here
} );

// other module's defininations ...

param:

  • gulp.src: you should read the main js file which you seajs.use
  • mainID: the main Module ID for the seajs app entrance. ~~Should be an absolute path based on your project~~ both relative path and abslute path are supported. but relative path will based on your sea.js file, it brings more complexity

feature:

  • receive the entry file stream and scan for all the require dependiences
  • scan require dependiences recursively
  • preserve modules whose id with {vars}, like load the specific i18n file, instead of caoncat all language file into final file
  • write dependience into defininations

haven't look into yet...

  • seajs.config.pathes
  • seajs.config.alias
  • other configs

about more knowledge about seajs modules and Naming Conventions, visit seajs docs