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-import-aliases

v1.0.2

Published

LESS plugin to use aliases in @importing files.

Downloads

4,923

Readme

less-import-aliases

Rewrite imports paths with defined alises

First of all, big thanks for less-plugin-npm-import, which this package relies on (paths replacement part).

During complex development, finally you will be having issues with LESS files organization. This plugin will help you have nice syntax of your paths (even relative to each other) thanks to aliases.

Usage

Instalation

npm install --save-dev less-import-aliases

Example files structure

Let's assume you have complicated files structure like this:

.
├── gulpfile.js
├── public
│   └── styles
│       ├── dest
│       └── src
│           ├── first_loader.less
│           └── second_loader.less
└── src
    └── bundles
        ├── FrontBundle
        │   └── styles
        │       └── less
        │           └── modules
        │               ├── module1
        │               │   ├── first_file.less
        │               │   └── second_file.less
        │               └── module2
        │                   ├── first_file.less
        │                   └── second_file.less
        └── OrderBundle
            └── styles
                └── less
                    └── modules
                        ├── module1
                        │   ├── first_file.less
                        │   └── second_file.less
                        └── module2
                            ├── first_file.less
                            └── second_file.less

PROBLEM

In this case you would be forced to create really awfull paths with some kind of relativity. It's always problematic.

Instead of using:

//first_loader.less
@import "../../../src/bundles/FrontBundle/styles/less/modules/module1/first_file.less"
@import "../../../src/bundles/OrderBundle/styles/less/modules/module1/first_file.less"
//FrontBundle -> first_file.less
@import "../../../../../OrderBundle/styles/less/modules/module1/first_file.less"

thanks to this plugin, you can just use:

//first_loader.less
@import "@FrontBundle/modules/module1/first_file.less"
@import "@OrderBundle/modules/module1/first_file.less"
//FrontBundle -> first_file.less
@import "@OrderBundle/modules/module1/first_file.less"

BE CAREFUL

If you want to use aliases, you have to type prefix - @ inside your LESS file; Not having this kind of notation could couse naming conflicts. You want to avoid it.

LESS PLUGIN (ex. gulpfile.js)

var getAliasFileManager = require('less-import-aliases');
    less = require('gulp-less');
var frontPath = __dirname + '/public/src/front_bundle/styles/less',
    orderPath = __dirname + '/public/src/order_bundle/styles/less';

gulp.task('compileLESS', function(){
  gulp.src(['public/styles/src/*.less'])
    .pipe(less({
        plugins: [new getAliasFileManager({
            aliases: {
                FrontBundle: frontPath,
                OrderBundle: orderPath
            }
        })]
    }))
    .pipe(gulp.dest('public/styles/dist'));
});

API

less-import-aliases ought to be called with Object as:

{
    alias: path_to_this_alias,
    alias_second: path_to_this_alias_second
}

The key has to be used without "at[@]" prefix