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

jsic

v0.1.6

Published

JS Import Compiler optimizes JavaScript by inlining recursively JavaScript files referenced by $import function

Downloads

9

Readme

JS Import Compiler

JS Import Compiler is a node.js application that looks for $import calls recursively in the source JavaScript file and resolves them in the destination file the same way as LESS/SCSS preprocessors resolve @import rule in the output CSS.

Why not AMD?

  • JSCS gives a way to reduce the number of HTTP requests by combining all scripts into a single one, what increases the application performance
  • Being a build tool JSCS doesn't require any additional JavaScript on client-side

Usage

Define dependencies in your code:

src/main.js

var foo = $import( "./Form/Input/Tel" );

Create the dependency source:

src/Form/Input/Tel.js

function() {
    return {
          prop: "",
          method: function(){}
    }
}

Run the compiler:

node jsic.js src/main.js build/mail.js

Examine the combined file:

build/main.js

var foo = function() {
    return {
          prop: "",
          method: function(){}
    }
};

Linter compatibility

In order to have keep dependency source in in valid syntax from a linter prospective you can assign its body to module.exports, which is ignored by the compiler

/**
* The banner will be ignored by compiler
*/
module.exports = function() {
    return {
          prop: "",
          method: function(){}
    }
};

JSIC as a grunt task

Please find instructions at https://github.com/dsheiko/grunt-jsic