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

mongoose_record_replay

v0.0.14

Published

readonly mongoose drop in for testing (replaying w.o. mongo db) and recording (running against mongodb)

Downloads

20

Readme

mongoose_record_replay Build StatusCoverage Status

readonly mongoose drop in for testing ( and recording test data )

Allows to record query results,

#usage

var mongoose = require('mongoose_record_replay').instrumentMongoose(require('mongoose'));

##extended usage: Behaviour can be set by environment variables ( see below) or explicitly via paramter:

var mode = 'REPLAY';
if (process.env.MYSWITCH) {
  mode = 'RECORD';
}
var mongoose = require('mongoose_record_replay').instrumentMongoose(require('mongoose'),
  'node_modules/mgnlq_testmodel_replay/mgrecrep/',
  mode);

var mongoose = require('mongoose_record_replay').instrumentMongoose(require('mongoose'));




currently supported methods:

1. <Model>.find().lean().exec().then (...)#
2. <Model>.aggregate().then( ... )
3. <Model>.distinct( ).then( ... )


# Modes

The operational mode is controlled by the environment variable
``MONGO_RECORD_REPLAY``

## Original mongoose

## Replaying  (``set MONGO_RECORD_REPLAY=REPLAY``)

 Connection establishing is suppressed!

 operation <Model>.find, <Model>.aggregate, <Model>.distinct
 return there recorded result ( if found ) or an
 ENOENT message on the file

 (set debug=mongoose_rec* ) to get more infomration


## Recording  (``set MONGO_RECORD_REPLAY=RECORD``)

Queries are executed against mongoose,
1.  query input
    * ``<modelname>``,
    * `<operation> (e.g. `find, aggregate, distinct`),
    * `<query/pipeline>` argumetns are recorded )
and
2. Result is recorded and stored.



## Recording location



On recording, files are created in (default locattion "mgrecrep/", can be controlled )

    1. mgrecrep/queries.json
        List of queries recorded
        could be used to refire them and update with new data.
        (=> nice feature)

    2. mgrecrep/data/<uniqueid>



The default folder can be changed via environment variables
``MONGO_RECORD_REPLAY_PATH``:

The variable value shall end with a terminating '/' !


    1. default mgrecrep
    2. Environment variable ``MONGO_RECORD_REPLAY_FOLDER``, e.g.
       ```
       process.env.MONGO_RECORD_REPLAY_FOLDER= mgrecrep/
       set MONGO_RECORD_REPLOAY_FOLDER=mypath/myfolder/
       export MONGO_RECORD_REPLAY_FOLRDER  mypath/myfolder/
       ```


    3. explicit path as 2nd argument to ``intrumentMongoose``

        ```javascript
        const recordFolder = './myfolder/';
        var mongoose = require('mongoose_record_replay').instrumentMongoose(require('mongoose'), recordFolder);
        ```



# Caveats / Known issues

 1. Beware: JSON serialization destroys differences between null and undefined etc.
 2. Currently returning full model documents is not supported,
    only the lean().exec promise chain

# Extends

feel free to record issue and provide pull request