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

sloppy-module-parser

v2.1.0

Published

Parse imports/exports/requires with a focus on speed over 100% correctness

Downloads

6,931

Readme

sloppy-module-parser

Parse imports/exports/requires with a focus on speed over 100% correctness

npm install sloppy-module-parser

Sometimes it might report requires that are indeed not requires but tries to not miss any. This limitation gives it a massive speed boost compared to other parsers.

Usage

const { init, parse } = require('sloppy-module-parser')

await init() // needed to init the async esm parser used

console.log(parse(src))

API

async parser.init()

Init the async esm parser. Call this before using the module.

const res = parser.parse(src, type = 'module', strictMode = true)

Parses imports/requires from the source. type helps it understand what it should parse for.

Type should be one of the following: module / script / json.

If strict mode is false, and type is not module, it autodetects if any import / export statements are used and if so auto corrects the type. This is useful for module interop.

The returned result looks like this

{
  type: 'module',
  resolutions: [
    {
      isImport: boolean, // is it an import or a require
      isAddon: boolean, // is this import / require pointing to a native addon
      position: [statementStart, inputStart, inputEnd], // where is the statement, might be null
      input: string, // the input to import / require, `null` is if it is unknown at parse time
      output: null // what it should resolve to, just set for conveinience
    },
    ...
  ],
  namedImports: [
    {
      isWildcard: boolean, // is it a wildcard import
      isExport: boolean, // reexports the import
      names: [string, ...], // the named imports,
      from: referenceToRelevantResolution
    }
  ],
  exports: [string, ...] // only default populated for esm
}

const exports = parser.exports(src, type)

Get the exports from a module. Type is the same as in parse.

License

Apache-2.0