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

gatsby-plugin-stylus-resources

v2.0.7

Published

Gatsby support for Stylus with resources (e.g. variables, mixins etc.)

Downloads

450

Readme

This is an extended version of gatsby-plugin-stylus.

The only difference is the use of sass-resources-loader so you can use your shared variables & mixins across all .styl files without manually importing them in each file.

Feel free to check out and run the example folder for detailed configuration.

Install

⚠️ BREAKING CHANGE : v2 uses [email protected] which requires Webpack 5 minimun (included in Gatsby v3)

For Gatsby v3

npm i gatsby-plugin-stylus-resources -d

or

yarn add gatsby-plugin-stylus-resources -D

For Gatsby v2

npm i [email protected] -d

or

yarn add [email protected] -D

Usage

  1. Create your file (or files) with resources :

    /* styles/config/mixins.styl */
    
    flexbox($value = row)
        display: flex
        flex-direction: $value
    
    truncate($fontsize = 14px)
        flexbox()
        height: $fontsize + 4px
        white-space: nowrap
        overflow: hidden
        text-overflow: ellipsis
  2. Include the plugin in your gatsby-config.js file :

    /* gatsby-config.js */
    
    module.exports = {
      plugins: [
        {
          resolve: "gatsby-plugin-stylus-resources",
          options: {
            resources: ['./src/styles/config/mixins.styl', 'path/to/another/file.styl'],
          },
        },
      ],
    }

⚠️ Do not include anything that will be actually rendered in CSS, because it will be added to every imported .styl file.

Without CSS Modules

// in gatsby-config.js
plugins: [`gatsby-plugin-stylus-resources`]

With CSS Modules

Using CSS modules requires no additional configuration. Simply prepend .module to the extension. For example: App.styl -> App.module.styl. Any file with the module extension will use CSS modules.

With Stylus plugins

This plugin has the same API as stylus-loader, which means you can add stylus plugins with use:

// in gatsby-config.js
const rupture = require("rupture")

module.exports = {
  plugins: [
    {
      resolve: "gatsby-plugin-stylus-resources",
      options: {
        use: [rupture()],
      },
    },
  ],
}

PostCSS plugins

PostCSS is also included to handle some default optimizations like autoprefixing a and common cross-browser flexbox bugs. Normally you don't need to think about it, but if you'd prefer to add additional postprocessing to your Stylus output you can sepecify plugins in the plugin options

// in gatsby-config.js
plugins: [
  {
    resolve: `gatsby-plugin-stylus-resources`,
    options: {
      postCssPlugins: [somePostCssPlugin()],
    },
  },
]

Contributing

Contributions are welcome ! See contributing guidelines

License

MIT

Copyright (c) 2019 Jimmy Beldone