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

idsk-elements-sass

v4.1.2

Published

ID-SK elements Sass files

Downloads

27

Readme

ID-SK Elements Sass

Installation

npm install idsk-elements-sass

Usage

Include all Sass files

@import idsk-elements;

Include individual Sass files

Choose partials from:

/public/sass/elements/.

Dependencies

ID-SK elements has the ID-SK frontend toolkit as a dependency.

npm install idsk_frontend_toolkit

The ID-SK frontend toolkit scss dependencies listed below must be imported before any idsk-elements partials.

// Settings (variables)
@import "colours";                                // Colour variables
@import "font_stack";                             // Font family variables
@import "measurements";                           // Widths and gutter variables

// Mixins
@import "conditionals";                           // Media query mixin
@import "device-pixels";                          // Retina image mixin
@import "grid_layout";                            // Basic grid layout mixin
@import "typography";                             // Core bold and heading mixins
@import "shims";                                  // Inline block mixin, clearfix placeholder

// Mixins to generate components (chunks of UI)
@import "design-patterns/alpha-beta";             // Only required if using _phase-banner.scss
@import "design-patterns/buttons";                // Only required if using _buttons.scss

// Functions
// @import "url-helpers";                         // Function to output image-url, or prefixed path (Rails and Compass only)

It assumes your project is using ID-SK template.

Configuration

Set a path for your image assets

The _url-helpers.scss partial requires that $path is defined in your main application stylesheet.

 $path: "/public/images/";

Ensure base styles are set

If you are not using ID-SK template.

Uncomment the base partial in _idsk_elements.scss:

// @import "elements/idsk-template-base";          // HTML elements, set by the ID-SK template

Compiling the Sass files

Add the node_modules/idsk_frontend_toolkit and node_modules/idsk-elements-sass directories to the includePaths property of your Sass plugin - if you're using a task runner like Gulp or Grunt, to reference the location of these files.

Folder structure

- index.html
-- node_modules
    -- idsk-elements-sass
    -- idsk_frontend_toolkit
-- assets
    -- scss
        - main.scss
    -- css
        - main.css

Using Gulp

const gulp = require('gulp')
const sass = require('gulp-sass')

// Compile scss files to css
gulp.task('styles', () => {
  return gulp.src('./sass/**/*.scss')
    .pipe(sass({
      includePaths: [
        'node_modules/idsk_frontend_toolkit/stylesheets', // 1
        'node_modules/idsk-elements-sass/public/sass'     // 2
      ]
    }).on('error', sass.logError))
    .pipe(gulp.dest('./css'))
})

In the example above includePaths uses two paths to resolve the scss @import statements.

  1. The location of the directory containing the idsk_frontend_toolkit sass files.
  2. The location of the directory containing the idsk-elements-sass files.

Using Grunt

grunt.loadNpmTasks('grunt-contrib-sass')

grunt.initConfig({
  sass: {
    dist: {
      options: {
        includePaths: [
          'node_modules/idsk_frontend_toolkit/stylesheets', // 1
          'node_modules/idsk-elements-sass/public/sass'     // 2
        ],
      },
      files: {
        'main.css': 'main.scss'
      }
    }
  }
})

In the example above includePaths uses two paths to resolve the scss @import statements.

  1. The location of the directory containing the idsk_frontend_toolkit sass files.
  2. The location of the directory containing the idsk-elements-sass files.

Contributing

You can find contribution guidelines in CONTRIBUTING.md