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

@justeat/f-build-scss

v0.12.0

Published

Fozzie Build configuration for Sass components

Downloads

42

Readme


npm version Build Status Coverage Status Known Vulnerabilities


Quick Guide

This module essentially finds and generates an Array of webpack-chain config objects, a builder for which is returned when this module is called.

Ideally, we would use one webpack-chain object with multiple entry points (to avoid duplication), but due to a bug in Eyeglass this isn't possible (as it returns the same output for the multiple CSS outputs). This also in turn means that we cannot generate a single manifest as a result of the CSS bundling, but rather need to generate one for each entry file (i.e., je.css, je.menulog.css), to be combined by the consuming application after the webpack build is finished.

Example Usage

To run as part of a webpack build, the following gives an example of how the style config can be applied.

const styleConfigBuilder = require('@justeat/f-build-scss'); // returns an array of webpack-chain objects

module.exports = (env, argv) => {
    const mode = settings.returnMode(argv);
    const styleConfig = styleConfigBuilder(mode);

    // Use map to apply common config to multiple webpack configs
    const rawStyleConfig = styleConfig.map(config => {
        config
          .mode(mode)
          .output
          .path(path.join(__dirname, 'wwwroot/hw'))
          .publicPath('/');

        return config.toConfig(); // Convert the webpack-chain object to a regular webpack config object
    });

    return [
        ...rawStyleConfig
    ];
};