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 🙏

© 2026 – Pkg Stats / Ryan Hefner

serverless-plugin-neo

v0.3.2

Published

Serverless plugin that compiles TypeScript code and bundles dependencies with node-file-trace

Readme

Serverless Plugin Neo

Serverless plugin that compiles TypeScript code and bundles dependencies with node-file-trace

This plugin was originally based on serverless-plugin-typescript and offers the following benefits:

  • Significantly smaller packages
  • Monorepo support

Known Issues

:warning: This plugin is still in the early stages of development and some things might not work

  • Only AWS is supported
  • Individual packaging has not been tested

Usage

  1. Install the plugin

    npm install serverless-plugin-neo
  2. Add plugin to Serverless Config file

    plugins:
      - serverless-plugin-neo
      ...
      - serverless-offline

    If you're using the serverless-offline plugin make sure it goes after serverless-plugin-neo

  3. Configure plugin (optional)

    custom:
      serverless-plugin-neo:
        baseDirectory: '.'
        tsconfig: 'tsconfig.json'

    There are no required settings. You can see a list of all settings and their defaults below.

  4. Build your code

    serverless package

Settings

| Name | Type | Default | Description | | --------------- | -------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | baseDirectory | string | process.cwd() | Your project's root directory. Defaults to process.cwd in a single repo project. Attempts to find the root package.json in a monorepo project. | | excludePackages | string[] | **/aws-sdk/**/* | A list of packages to exclude from bundling. See the node-file-trace docs for details. | | skipCleanup | boolean | false | Clean up .build directory after packaging. Disabling this can be useful for troubleshooting build issues. | | tsconfig | string | tsconfig.json | tsconfig filename |

Contributing

If you'd like to contribute to this project we recommend that you first open an issue to discuss your proposed change.

  1. Fork this repo
  2. Clone the forked repo
  3. Install dependencies: npm install

Development

npm start

Building

npm run build

To clean the build directory run npm run clean

Testing

npm run test

Publishing

  1. Update the version in package.json
  2. Add an entry in CHANGELOG.md
  3. Commit your changes
  4. Run npm pack --dry-run to see what will be published
  5. Run npm publish
  6. Create a release on GitHub. Use the version as the tag and release name. For example for version 1.0.0 the tag and release name would be v1.0.0.