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-remain-exports

v1.2.4

Published

vite plugin that remain exports from html-entry-script

Downloads

20

Readme

简体中文 | English

Vite-Plugin-Remain-Exports

This plugin is aimed to remaining the exports from entry scripts that imported by entry HTML.

1. Use case

It is important for those micro frond-end project builded with ES-Module style.

Some micro frond-end framework, like IceStark, need each micro modules export two life-cycle: mount and unmount.

If entry scripts can't export those two life-cycle, the micro module would't been rendered to page.

2. Usage

2.1 Install

npm i -D vite-plugin-remain-exports
yarn add -D vite-plugin-remain-exports
pnpm i -D vite-plugin-remain-exports

2.2 Using plugin

import remainExports from 'vite-plugin-remain-exports'

// @see https://vitejs.dev/config/
export default defineConfig({
  plugins: [
    // ...other plugins
    remainExports(),
  ],
})

3. Core Theory

As follow, it is an entry html in vite project:

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <link rel="icon" type="image/svg+xml" href="/src/favicon.svg" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Vite App</title>
  </head>
  <body>
    <div id="root"></div>
    <script type="module" src="/src/main.tsx"></script>
  </body>
</html>

And the entry scripts imported by entry html is /src/main.tsx.

3.1 How entry html was handled by vite

By default, vite will transfer the entry html to the following js code:

import "vite/modulepreload-polyfill";

import "/src/main.tsx";

The build process of vite is based on rollup. For the rollup project, entry html is the entry file. And in the build process, rollup will only remain the exports of entry file, then tree-shaking other depends.

So for remaining the entry scripts (main.tsx) exports, we need some magic. Here leading in a concept -- module double.

3.2 Module double

// index.ts
export * from 'another.ts'

// another.ts
export const demo = 1;

For importers, index.ts and another.ts is working the same.

3.3 Plugin core

After introducing how entry html was handled by vite and the module double concept, we can modify the transfer result of entry html, as following:

export * from "vite/modulepreload-polyfill";

export * from "/src/main.tsx";

Thus, for vite user, the entry scripts (main.tsx)work as the entry file, and the exports of them will can be remained.