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

vite-plugin-conditional-compiler-ex

v0.1.13

Published

<p align="center"> <img width="300" src="./assets/logo.svg" alt="logo of vite-plugin-conditional-compiler repository"> </p>

Downloads

7

Readme

New Feature

Support condition inline.

First, config env variable, in file: "/.env.development"

VITE_TEST=true

Then, in *.vue file:

// example 1
const isTest = /* v-ifdef VITE_TEST=true */ true /* v-else */ false /* v-endif */;

// example 2
const myFunction = /* v-ifdef VITE_TEST */ async /* v-endif */ () => {
  /* v-ifdef VITE_TEST */ await doSomeTestThings(); /* v-endif */
  doOtherThings();
};

Installation

pnpm i -D vite-plugin-conditional-compiler-ex

Usage

// vite.config.ts
import { defineConfig } from "vite";
import ConditionalCompile from "vite-plugin-conditional-compiler-ex";

export default defineConfig({
  plugins: [ConditionalCompile()],
});

Syntax

Start with #v-ifdef or #v-ifndef, then append %ENV%, end with #v-endif, you can also use #v-else.

  • #v-ifdef: if defined
  • #v-ifndef: if not defined
  • %ENV% Vite environment variables

Warning The #v-ifndef is deprecated in the next version, maybe :)

Configuration

export interface Options {
  /**
   * @default ["**/*"]
   */
  include: FilterPattern;
  /**
   * @default []
   */
  exclude: FilterPattern;
}

Other Example

// Compile in production environment only
// #v-ifdef PROD
value = 1;
// #v-endif
/* Compile in red except for development environments, otherwise white */
.code {
  /* #v-ifndef DEV */
  color: red;
  /* #v-else */
  color: white;
  /* #v-endif */
}
// Condition or, not supported &&
// Compile in production or development
// #v-ifdef PROD||DEV
value = 1;
// #v-endif
// Allow custom environment variables
// Compile only when 'VITE_MY_ENV' exists and is not false
// #v-ifdef VITE_MY_ENV
value = 1;
// #v-endif
// Allow specified values
// Compile only when 'VITE_MY_ENV' exists and is not equal to hi
// #v-ifdef VITE_MY_ENV!=hi
value = 1;
// #v-endif

Other

With the better-comments plugin in VsCode, syntax can be highlighted

{
  "tag": "#v",
  "color": "#666",
  "strikethrough": false,
  "underline": false,
  "bold": true,
  "italic": false
}