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

code-injector

v0.0.3

Published

A library make use of gulp to generator code to specified code block.

Downloads

9

Readme

Code Injector

A library used to generate code and inject them in target code block so that you could feel like make use of NodeJS in browser side.

People nowadays use webpack more frequently than gulp. However, webpack, most of the time, makes use of babel to transform (compile) code in memory or build files in production stage. These transformed codes are invisible as we cannot see or use them directly. Therefore, babel plugins sometimes may be misleading and that's the reason why I choose gulp rather than webpack or babel to achieve the purpose of code injection.

Quick Start

npm install code-injector -g

code-injector # wait a moment brefore you do this

Command

Usage: index [options]

Options:

-h, --help         output usage information
-V, --version      output the version number
-c, --config-path  config file, default path is generator.config.js

Config File

Before you run the code-injector command, you will need to prepare a config file at the root of your project and named it generator.config.js.

A few rules you need to code and understand in this file:

/**
* a useful function that could be used to generator any code you want
* @type {[*]}
*/
export function generatorStart() {
    return `console.time();`;
}
/**
* a useful function that could be used to generator any code you want
* @type {[*]}
*/
export function generatorEnd() {
    return `console.timeEnd();`;
}
/**
* required
* the file you want to watch and compile
*/
export const watchSrc = [`./test/index.js`];
/**
* default: generator
* prefix used to indicate which function is going to be used
* e.g. generatorTest
*/
export const prefix = `generator`;

Code Block

The previous part has defined generatorStart and generatorEnd. So start represents its function return value console.time(), whereas end represents its function return value console.endTime(), so you could define the code block like this,

/* inject:start */
/* end-inject */

// WRITE YOU OWN CODE HERE

/* inject:end */
/* end-inject */

Start Now

Now you can run the command:

code-injector

TODO List

  • [ ] only compile the when the code block changed

License

MIT