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-civet

v0.2.8

Published

Vite plugin for civet

Downloads

20

Readme

:warning: UNMAINTAINED This plugin is not actively maintained. Please migrate to the offically supported unplugin-civet


vite-plugin-civet

Experimental vite plugin for Civet.

Civet is a new programming language that transpiles to TypeScript/JavaScript. It borrows many features from CoffeeScript, imba etc. and offers type-safety through TypeScript integration. With this plugin you can use civet in a vite project. You can use civet for your entire application or a subset of modules.

Installation

Install it as a dev dependency through your preferred package manager (we recommend pnpm)

npm install -D vite-plugin-civet

# or
pnpm install -D vite-plugin-civet

# or
yarn add -D vite-plugin-civet

Usage

Here is a simple example of a vite.config.ts, with no processing beyond Civet:

import { defineConfig } from 'vite'
import civetPlugin from 'vite-plugin-civet'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    civetPlugin({
      // Remove TypeScript type annotations from output
      stripTypes: true,
    }),
  ],
})

It is recommended that type checking is performed separately (either through editor integration or Civet CLI rather than as part of build).

Integrations

Please note that civet (by design) does not include polyfills for older browsers. Nor does it have built-in support for transpiling non-standard JavaScript features like JSX to standard JavaScript.

While Civet offers syntax support for JSX, it does not make any assumptions around what that JSX will compile to. You will need additional framework-specific plugins to process the output of civet to standard JavaScript.

The following example vite.config.ts illustrates how this plugin can integrate with vite-plugin-react-swc.

import { defineConfig } from 'vite'
import reactPlugin from '@vitejs/plugin-react-swc'
import civetPlugin from 'vite-plugin-civet'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    reactPlugin(),
    civetPlugin({
      stripTypes: true,

      // Civet plugin needs to be made aware of the plugin
      // that will support TypeScript compilation
      outputTransformerPlugin: 'vite:react-swc',

      // Currently vite-plugin-react will not perform
      // any transformations unless file extension is js/jsx etc.
      //
      // So we need to change extension before passing
      // result of civet transformation to the plugin
      outputExtension: 'jsx',
    }),
  ],
})

Note that the id here is the Vite plugin id, different from the name of the package that defines the plugin. This id can be found in the object that the plugin's default export returns.

> (await import('@vitejs/plugin-react-swc')).default({})
[
  {
    name: 'vite:react-swc',  // <------
    apply: 'serve',
    ...
  },
  {
    name: 'vite:react-swc',
    apply: 'build',
    ...
  }
]

It should be possible to integrate plugins for other frameworks too in similar fashion. Please open an issue describing your use case if you face an issue.

Sample projects

Sample framework specific projects are available to help you get started quickly:

  • React (Frontend): npx degit lorefnon/vite-plugin-civet/playground-react-babel my-app
  • Solid (Frontend): npx degit lorefnon/vite-plugin-civet/playground-solid my-app

Astro

You can use this plugin with Astro and its Integrations for JSX support by referring to the astro:jsx plugin. Here is an example astro.config.mjs using the SolidJS integration:

import { defineConfig } from 'astro/config'
import civetPlugin from 'vite-plugin-civet'
import solidJs from "@astrojs/solid-js"

// https://astro.build/config
export default defineConfig({
  vite: {
    plugins: [civetPlugin({
      stripTypes: false,
      outputExtension: 'tsx',
      outputTransformerPlugin: 'astro:jsx',
    })]
  },
  integrations: [solidJs()]
});

TODO

  • [ ] Sourcemap integration

LICENSE (MIT)