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

mockfc

v0.0.8

Published

mock file for fc

Downloads

11

Readme

mock

mock by reverve-proxy

install

npm install mockfc

or

npm install git://github.com/linkwisdom/mock.git

usage

var mock = require('./index');

// redirect localhost/note/** to blog.liandong.org/blog
// the request response by the back-end-proxy

var proxyConfig = {
    host: 'bd.liandong.org',
    port: 80,
   // path: ['/project'],
   // cookie: {name:'linkwisdom'},
    replace: [
        {source: '/project/114', target: '/project/114'}
    ]
};


var config = {
    service: 'getFile',
    port: 8080,
    dir: './',
    proxy: proxyConfig
};

mock.startServer(config);

run intant js apps on your server

  • config your server .

    { location: //request.ajax/, handler: mock.runJS({sourceDir: './debug/response'}) }

  • make sure that your request has parameter path and post-data parameter param nodejs run the jsfile content with runInNewContext to make sure your mock program run instant without restart your server it's easy to write in mock-program

.

console.log({msg: 'the first message'});
  • souds too easy, follow objects are eported for you path: the request-path param: the post-data console.log: you just need log your data, eaquals console.dump

  • you also can customize your mock apps for mock.runJs arguments

.

mock.runJS = function(param);
param.sourceDir
param.runJS = function(code, path, param)
param.pack  = function(data) 
param.getContent = function(pathName, param)
param.getResult = function(pathName, param)
  • for more detail knowleade, you can learn it from the source code

test for edp project

  • config your edp config file
  • make sure that request send normally

.

{
    location: /\/request\.ajax/,
    handler: mock.getQuery(response)
}
  • you can test by on your *nix system as

    curl -d 'path=GET%2Fmaterial&userid=5&params={"level":"planinfo","fields":["optsug","planid"]}' http://localhost:8188/request.ajax

  • where response with function return json or string

.

exports.response = function(path, params) {
    return {
        status: 200,
        data: [ ... ]
    };
}