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

@umu-team/preprocess-loader

v0.1.2

Published

umu 条件编译

Downloads

2

Readme

@umu-team/preprocess-loader

条件编译

npm package npm package

Install

npm i -D @umu-team/preprocess-loader

Usage

webpack 中的配置:

webpack.config.js

module.exports = {
  module: {
    rules: [
      {
        test: /\.jsx?$/,
        use: [
          'ts-loader',
          {
            loader: '@umu-team/preprocess-loader',
            options: {
              context: {
                IS_PRODUCTION: true
                ...
              },
            },
          },
        ],
      },
    ];
  }
}

假设页面代码中可使用的编译参数为:

  • SYSTEM 当前系统
  • LOCALE 当前语言
  • DEBUG 是否调试模式,可进行测试代码相关的控制
  • IS_PRODUCTION 区分线上与线下环境

示例:

// @if LOCALE = 'JP'
console.log('当前语言:日语')
//@endif

// @if LOCALE != 'JP'
console.log('当前语言:非日语')
//@endif

// @if IS_PRODUCTION
console.log('线上环境')
//@endif

// @if !IS_PRODUCTION
console.log('线下环境')
//@endif

具体使用详见 preprocess

已知问题

与 Sass 配合使用时,因为 sass 文件中通过 @import 导入的文件是 sass 自己处理的,而非 webpack。 即 webpack 不能分析 sass 文件中的引用关系,所以 webpack 的 loader 只作用于 js 中直接引用进来的 sass 文件, 而这个 sass 文件中如果还 @import 了其他 sass 文件,后续这些文件不会被 load 处理。

示例:

index.jsx

import './index.scss'

index.scss

@import './other.scss'
body{
  color:red;
}

other.scss

/* @if IS_PRODUCTION */
body{
  color: blue;
}
/* @endif */

other.scss 中的条件编译不会生效,因为它是在 sass 文件中通过 @import 句法导入到项目中的,没有被 webpack 分析到。

所以,为了解决上述问题,其他 loader 应该在 sass-loader 之后调用。

示例:

{
  test: /\.scss$/,
  use: [
      {
        loader: "css-loader",
        options: {
          importLoaders: 2
        }
      },
      {
        loader: "@umu-team/preprocess-loader", // 此时拿到的是处理过 `@import` 完整的 sass 文件
        options: {
          context: {
            IS_PRODUCTION: env.IS_PRODUCTION
          }
        }
      },
      "sass-loader" // sass-loader 先处理 sass 文件,将导入合成一个文件传递给下游其他 loader
    ]
}

同时,sass 文件中注释需使用多行注释的方式 /* */ 而不是 // 开头的单行注释。