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

rollup-plugin-code-deleter

v0.0.4

Published

A rollup plugin to delete code by Comments

Downloads

6

Readme

rollup-plugin-code-deleter

NPM Version NPM Downloads bundle JSDocs License

A rollup plugin to delete code by Comments WIP

Why

Maybe you have a common package that is used by multiple packages,like this:

// package A
function renderForPackageB() {
  // ...more codes
}
function renderForPackageC() {
  // ...more codes
}

export const obj = {
  renderForPackageB,
  renderForPackageC,
  ...someOtherProperties
}
// package B
import { obj } from 'A'
obj.renderForPackageB()
// package C
import { obj } from 'A'
obj.renderForPackageC()

If you only build package B, the renderForPackageC will also be in your bundle. The tree-shaking will not work, all codes used in renderForPackageC will bu in bundle.

If you know renderForPackageC does't need in your bundle. you can delete it from obj, to help you shrink the size of your bundle.

Install

npm install rollup-plugin-code-deleter --save-dev

Usage

In Rollup

import codeDeleter from 'rollup-plugin-code-deleter'

export default {
  input: 'src/index.js',
  output: {
    file: 'dist/app.js',
    format: 'umd',
    name: 'app'
  },
  plugins: [
    codeDeleter()
  ]
}

In Vite

import { defineConfig } from 'vite'
import codeDeleter from 'rollup-plugin-code-deleter'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [CodeDeleter()],
})

In Code

you can comment the code where you want to delete

const obj = {
  /** code-deleter */
  a: 1 // the property will be deleted
}

also you can specify which piece of code is deleted

const obj = {
  /** code-deleter: pc */
  a: 1,
  /** code-deleter: mobile */
  b: 2
}

with config:

import codeDeleter from 'rollup-plugin-code-deleter'
export default {
  plugins: [
    codeDeleter({
      delete: ['pc']
    })
  ]
}

the code will output

const obj = {
  /** code-deleter: mobile */
  b: 2
}

License

MIT License © 2023-PRESENT ShunJun