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

piral-cli-vite

v1.2.0

Published

Provides debug and build capabilities for pilets and Piral instances using Vite.

Downloads

544

Readme

Piral Logo

Piral CLI Vite · GitHub License npm version tested with jest Gitter Chat

This plugin enables using Vite as the bundler for Piral instances and pilets.

Installation

Use your favorite npm client for the installation:

npm i piral-cli-vite --save-dev

Note: If you don't install any bundler for use in piral-cli then piral-cli-vite will be automatically installed for you.

Using

There is nothing to do. Standard commands such as piral build or pilet debug will now work with Vite as the bundler.

This plugin comes with batteries included. You don't need to install or specify your Vite version.

What's Inside

Right now it includes:

  • vite-plugin-codegen
  • vite-plugin-environment

Additionally, most known referenced assets are handled as files.

As such it should be prepared to include assets (images, videos, ...), stylesheets (CSS and SASS), and work with TypeScript.

Public Folder

By default the source folder (e.g., /src) is set as root. Therefore, the src/public folder (if available) will be used for the public assets. If you want to change this you can use a custom Vite config as explained below, e.g.:

import { resolve } from 'path';

export default {
  publicDir: resolve(__dirname, 'public'),
}

Referencing Scripts

Vite uses all scripts with type=module to be entry points in the index.html file. However, as you might just have scaffolded a solution or are more used to simply have <script src="./index.tsx"> in your HTML file we patch the index.html to match exactly that. Nevertheless, this creates a problem if you want to, for instance, reference some scripts that should not be part of the bundling (or would only exist later).

One thing to do here is to put some attribute to the script, i.e., transform

<script src="./do-not-pick-up.js"></script>

to

<!-- version below if order and immediate are relevant -->
<script blocking src="./do-not-bundle.js"></script>
<!-- version below if order is relevant, but immediate is not relevant -->
<script defer src="./do-not-bundle.js"></script>
<!-- version below if order and immediate are irrelevant -->
<script async src="./do-not-bundle.js"></script>

Customizing

If you want to customize the given config (e.g., to add more plugins) then create a file vite.config.js (or anything else accepted by Vite, e.g., vite.config.ts) in your root directory.

In the most trivial version the file looks as follows:

import { defineConfig } from 'vite';

export default defineConfig({
  // Your config additions here
});

If you want to add some plugin you could do:

import { defineConfig } from "vite";
import legacy from "@vitejs/plugin-legacy";

export default defineConfig({
  plugins: [
    legacy({
      targets: ['defaults', 'not IE 11'],
    }),
  ],
});

The configuration works with all formats that Vite supports.

License

Piral is released using the MIT license. For more information see the license file.