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

embed-shell

v1.0.0

Published

embed-shell ===========

Downloads

4

Readme

embed-shell

embed-shell is a utility module for embedding an interactive shell with some sane defaults. Anytime .clear is used within the shell it will reset the context to the initial state and will clear the require.cache of references to modules not loaded from node_modules. The .clearCache command will reset the require.cache but will otherwise leave the repl context unchanged.

If you use mongoose be aware that resetting the context will also reset the state of any Model registred to any Connection. If you create the server with a fully qualified path to a file that initializes your models this will be required after the context has been cleared.

Currently node supports await within the top level of a REPL only if invoked with --experimental-repl-await. A REPL shell created by this module will, by default, monitor the shell context and if a promise is assigned to a variable it will add a then handler that will upon either resolve/reject of the promise assign the result to the context variable. If the rejection is an object it will assign true to the __rejected property of that object.

Events

| event | callback | notes | |------------|---------------------|-------| | cleared | (ctx: repl.Context) | emitted after clearing the require.cache you can listen to this event to do additional customization of the context. | | reset | (ctx: repl.Context) | emitted after the context has been cleared. (Any mongoose models and schemas are cleared prior to the reset event being emitted. If you supplied a path to a file that can refresh them it will be required.) | | shutdown | () | emitted when the repl exits or closes |

Usage

const path = require('path');
const { Server } = require('./');

const server = new Server(__dirname, {
  context: { active: true, name: 'Bob', occupation: 'Builder' },
  modelsPath: path.resolve(__dirname, 'test', 'fixtures', 'models'),
  prompt: 'example> ',
});

server.start();