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

@inveris/vite-plugin-virtual-resource

v2.0.0

Published

A vite plugin loader for virtual paths with resolvers.

Downloads

28

Readme

vite-plugin-virtual-resource

A vite plugin loader for virtual paths with resolvers.

Use import name from '~virtual/source' to include a non existant content that is loaded and transformed with a resolver.

V2 supports vite 4+. For previous vite version use [email protected]

Example

You need to include a svg icon from iconify icons framework. In your application you use your own component for output rendering (Icon-component) and you need only the raw svg-data. The raw-data comes from @iconify-json. The virtual-resource plugin resolves the svg-data (json). View exemples below.

It can resolve any resource, not only icons.

Install

npm install --save-dev @inveris/vite-plugin-virtual-resource

Usage

// vite.js
import { virtualResource } from '@inveris/vite-plugin-virtual-resource'

export default defineConfig({
  // ... vite config

  plugins: [
    virtualResource(),

    // ... other plugins
  ]
})

Without any options, virtual-resource uses a builtin resolver to include @iconify-json icon files and let you use it with import SomeIcon from '~/icon/PACKAGE/ICON_NAME'.

Example with default resolver (works with any framework: react, vue, svelte, ...)
import CloseIcon from '~icon/mdi/close-circle-outline'

<Icon src={CloseIcon} />

With virtual and custom resolver

// vite.js
import { virtualResource, resolver, virtuals } from '@inveris/vite-plugin-virtual-resource'

export default defineConfig({
  // ... vite config

  plugins: [
    virtualResource({
      virtuals: {
        // builtin
        '~icon/': virtuals.iconify,

        // builtin (long form)
        '~otherIconPackage/': {
          source: 'node_modules/@iconify-json/${1}/icons.json',
          match: /^.*?\/(.*?)\/(.*?)$/,
          resolver: resolver.iconify
        }

        // custom
        '~myicon/': {
          source: 'my-icon-dir/all-icons.json',
          match: /^.*?\/(.*?)$/,
          resolver: (source, matches, config) => {
            const name = matches[1]
            const allIcons = JSON.parse(fs.readFileSync(source, 'utf8'))
            return {
              code: 'export default \'' + allIcons[name] + '\''
            }
          }
        }
      }
    }),

    // ... other plugins
  ]
})

You can use your own resolver, view builtin-resolvers.ts for a complete example.

Example
import CloseIcon from '~icon/mdi/close-circle-outline'
import HelpIcon from '~otherIconPackage/mdi/help-circle-outline'
import MyIcon from '~myicon/loading'

<Icon src={CloseIcon} />
<Icon src={HelpIcon} />
<Icon src={MyIcon} />

FAQ

Why not use vite to include resources?

That's a part of the job of vite. But in some cases you need to load and resolve complex data, that is not direct possible in vite without a plugin.

Why not use unplugin-icons?

unplugin-icons is a great plugin to include (only?) icons as a component. But for each icon it generates a component. So each component increases the code size unnecessary. If you use your own Icon-component for output rendering, you need only the raw svg-data.