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

ymodules-loader

v1.0.2

Published

> Webpack loader for [ymodules](https://github.com/ymaps/modules) module definitions

Downloads

5

Readme

ymodules-loader Build Status

Webpack loader for ymodules module definitions

Getting started

npm install ymodules-loader --save-dev

Add the following into your loader list:

module: {
    loaders: [{
        test: /\.js$/,
        loader: 'ymodules-loader'
    }]
}

ProTip: add exclude: /node_modules/ if you don't need to look for that modules among vendor components

Then loader will pass through your js-files and detect all imports in ymodules format. All found dependencies would be added with require() call.

Source file

modules.define('example', ['dep1', 'dep2'], (provide, d1, d2) => {
    //...
});

Processed file

var modules = require('ym');

require('dep1/dep1');
require('dep2/dep2');

modules.define('example', ['dep1', 'dep2'], (provide, d1, d2) => {
    //...
});

After that webpack will find all your modules and put them together as well as usual CommonJS modules.

Example

See the test folder for real usage example.

Technical details

The code processing is performed by babel.

Now we are assuming that your modules placed by default bem-project structure like:

common.blocks/
├── button
│   └── button.js
├── input
│   └── input.js
└── select
    └── select.js

In future versions module path resolving will be configurable.