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

@stylable/experimental-loader

v6.1.1

Published

This loader supports working with `mini-css-extract-plugin`. Internally, this setup uses two separate loaders.

Downloads

203

Readme

Experimental Stylable Webpack Loader

This loader supports working with mini-css-extract-plugin. Internally, this setup uses two separate loaders.

  • stylable-transform-loader - responsible for Stylable transformations and generates the css-loader compatible output that the mini-css-extract-plugin expects
  • stylable-runtime-loader - Stylable offers a richer module API compared to css modules. The css-loader flow does not support this API, and so we are using this loader to convert the raw Stylable locals data to the appropriate runtime stylesheet

Disclaimer

This loader is experimental and currently not the recommended way of integrating Stylable into your project.
Use @stylable/webpack-plugin for the latest stable integration.

  • native css import is not supported

Example

A minimal webpack configuration using the two Stylable loaders in conjunction with the mini-css-extract-plugin loader:

const MiniCssExtractPlugin = require('mini-css-extract-plugin');
const { stylableLoaders } = require('@stylable/experimental-loader');

module.exports = {
  plugins: [new MiniCssExtractPlugin()],
  module: {
    rules: [
      {
        test: /\.st\.css$/i,
        use: [
          stylableLoaders.runtime(),
          MiniCssExtractPlugin.loader,
          stylableLoaders.transform(),
        ],
      },
      // load asset from CSS url()
      {
        test: /\.(png|jpg|gif)$/i,
        use: [
          {
            loader: 'url-loader',
            options: {
              limit: 8192,
            },
          },
        ],
      },
    ],
  },
};

Transform loader options

interface LoaderOptions {
  resolveNamespace?(namespace: string, filePath: string): string;
  filterUrls?(url: string, ctx: loader.LoaderContext): boolean;
  exportsOnly?: boolean;
  alwaysEmitErrors?: boolean;
}

| Option | Description | | ------------------ | --------------------------------------------- | | resolveNamespace | override default stylesheet namespace process | | filterUrls | filter urls from webpack process | | exportsOnly | only export the runtime stylesheet | | alwaysEmitErrors | always emit Stylable diagnostics as errors |

SSR (exportsOnly)

When building Stylable for consumption in a server-side renderer build, you may want to extract only the exports of the runtime stylesheets and not the content of their CSS. In such a case you would only be required to use the transform loader and the exportsOnly option.

{
  test: /\.st\.css$/i,
  use: [
    stylableLoaders.transform({ exportsOnly: true }),
  ],
}

Known issues

As opposed to the current webpack-plugin integration, some behaviors are still missing, or lacking:

  • The loader does not perform Stylable specific optimizations such as: minimizing namespaces and classNames, removing unused rules, and so on
  • May encounter issues with CSS loading order (order being determined by JS imports) - webpack open issue
  • May have issues with updating CSS when JS imports change order in dev time watch mode

License

Copyright (c) 2021 Wix.com Ltd. All Rights Reserved. Use of this source code is governed by a MIT license.