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

less-loader-plugins

v0.0.1

Published

LESS plugins for various loaders.

Downloads

2

Readme

less-loader-plugins

LESS plugins for various loaders.

While other plugins do exist online, the problem I've noticed with a lot of them is that they are over-complicated and inject automatically into the head tag. Because they automatically inject, this puts a runtime dependency on the plugin. Adding the style should be handled by the developer. All of these plugins work on that principle, and there's no plans to add this feature.

Why not use SASS and Webpack?

  • I prefer portability of code and not having to be forced to use certain tools to run my app in development.
  • There's really no noticeable performance difference whether or not the server does the compilation or the client does.
  • Have you seen the code for SASS on the browser? Impossible to debug if you run into issues. Also unsupported by the SASS team who are developing their tool using Ruby which is another tool that needs to be installed.
  • Commonly used functionality is practically identical between LESS and SASS.

Supported Loaders

less.amd.js

Used by Lamda or any other AMD loader. Configure your require configuration to add the following mappings:

var require = {
    paths: {
        "less": "<node_modules>/less/dist/less",
        "styles": '<node_modules>/less-loader-plugins/less.amd' 
    }  
};

You can then use the plugin syntax to load LESS files:

define([
    'styles!./MyStyles.less'
], function (styles) {
    // Attach styles to head tag. 
});

less.systemjs.js

Used by SystemJS. Configure the SystemJS configuration file to add the following mappings:

 System.config({
    paths: {
        'npm:': 'node_modules/'
    },

    map: {
        'styles': 'npm:less-loader-plugins/less.systemjs.js',
        'less': 'npm:less/dist/less.js'
    },
    packages: {
        src: {
            meta: {
                '*.less': {
                    loader: 'styles'
                }
            }
        }
    }
});

You can then import styles using the following in your code:

import styles from './MyStyles.less';

// Attach styles to head tag.