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

es6m2amd

v1.0.8

Published

ECMAScript 6 module to AMD converter

Downloads

4

Readme

ECMAScript6 module to AMD converter

Converts ECMAScript 6 modules to AMD.

Install

$ [sudo] npm install -g es6m2amd

Usage

$ m2amd -o out examples

Where "examples" is the directory which will be scanned for files and "out" is the folder, in which the processed files will be stored.

You can include only some of the files in a directory by specifying file pattern via "-i" option, like this:

$ m2amd -o out -i "**/module.js" examples

In this case only file, called "module.js" in whatever sub-directory of "examples" folder will be processed.

Source maps will be generated if you run the program with -m option.

Look for more information in the rest of the options:

$ m2amd --help

  Usage: m2amd [options] <folder ...>

  Options:

    -h, --help                     output usage information
    -o, --output [output folder]   output folder to store the generated AMD module. Default: current directory
    -i, --include [file patterns]  file patterns to process. Default: "**/*.js"
    -m, --map [source map]         Generate source map
    -V, --version                  output the version number

License

LGPL License

Build Status