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

@molecuel/mongodb

v2.2.2

Published

Molecuel MongoDb Module

Downloads

3

Readme

@molecuel/mongodb

NPM version Build Status Coverage percentage

mongodb module for the Molecuel framework

Build System

We are using npm to build the entire module. During development we use the tsc compiler defined in the task.json for visual studio code cause the incremental compilation is very fast. To start the build and watch process in Visual Studio Code just press CTRL+SHIFT+B. The build console should come up and show you the results of the build process. Any other editor can be used or just use tsc -w -p . on the commandline.

All available npm options:

npm run tslint

Executes the linter for the typescript files in the src folder

npm run tslint_test

Executes the linter for the typescript files in the test folder

npm run ts

Runs the Typescript compiler for all files in the src directory

npm run ts_test

Runs the Typescript compiler for all files in the test directory

npm run build

Executes thes linter for the files in the src folder and runs the typescript compiler for the files in the src folder.

npm run build_test

Executes thes linter for the files in the test folder and runs the typescript compiler for the files in the test folder.

npm run build_all

Executes thes linter for the files in the src and test folder and runs the typescript compiler for the files in the src and test folder.

npm run mocha

Just executes the local mocha command which relies in the local node_modules directory.

npm run test

Executes the compilation of the test files and runs the mocha test.

npm run cover

Runs the istanbuld code coverage test and remaps the results to the typescript sources

npm run remap

Remaps the code coverage report to typescript

npm run remaphtml

Remaps the html output of istanbul to the typescript sources

npm run remaplcov

Remaps the lcov reports to the typescript sources

npm run coveralls

Runs the code coverage reports, the remaps and send the results to the coveralls.io service

npm run createdoc

Creates the HTML for the API documentation in the docs folder. The docs folder is in .gitignore and not part of the master branch.

npm run publishdocs

Publishes the API documentation to the gh-pages branch.

npm run docs

Shortcut for createdocs and publishdocs

npm run 2npm

Checks it the package version in package.json is higher than the registered one in npm registry and published the package if the version is higher.

notes

using readonly copies of connections may result in exceptions from nodejs EventHandlers