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

@ugdu/packer

v2.0.0

Published

A packer to help develop and build micro frontends projects

Downloads

32

Readme

A packer powered by the task processor and the runtime helper to help develop and build micro frontends projects.

Overview

This packer provide some task options such as build, serve etc. You can use these task options, for example build, to create a task which could build your project for production. For features, check features. For a simple example, check usage. The phrases like vendor package are terms. Their brief explanation is here. For more detail, check our API docs.

Features

  • Minimal build time.
    • For your source code, only files changed will be rebuilt.
    • For vendor package, only packages whose version changes will be rebuilt.
  • Minimal generated files.
    • For vendor package, Only packages imported by multiple modules or local module will be built separately.
  • Minimal generated size.
    • For vendor package, only code used in your source code will be built into the generated files.
  • Security.
    • The package will be rebuilt when you import bindings that the corresponding generated module haven't export.
    • We will throw a meaningful error in build time other than runtime when you accidentally make a mistake.
  • Extensible
    • You can hook into the stage you are interested in when you develop an application.
    • You can enhance our built-in task options, or create your own. And then share to others.

Usage

Below is a quick start.

Note: @ugdu/processor and @ugdu/packer are exported in esm format. So we requires Node.js version >=14.17.0.

Install

Install pnpm

@ugdu/packer needs your project to be based on pnpm.

npm install -g pnpm

Install ugdu and vite

@ugdu/packer is powered by vite.

pnpm -Dw add @ugdu/processor @ugdu/packer vite

Recommend project structure

- packages  // Your `local package`s
  - container // The entry package of app. You may need multiple entry package if your project has more than one app.
  - components  // Common used components
  - utils // Common used utils
  - purchase  // Business packages
  - sale  // Business packages
- public  // Assets in this directory will be served at root path / during dev, and copied to the root of the dist directory as-is.
- scripts // task scripts
  - task.js
- index.html  // The info that will be used at runtime such as `importmap` and `ur.modules` will be injected to `index.html` automatically. We can consider it as our template. Note: Different with vue, we don't seem `index.html` as entry point. So we don't need to add corresponding script tag to references our source code.
- package.json  // To use the native esm on nodejs, we should specify the `type` field as `module`.
- pnpm-workspace.yaml // The pnpm workspace config file

Our index.html

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <link rel="icon" href="/favicon.ico" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>ugdu</title>
    <!-- Below script is our runtime lib -->
    <script async src="https://unpkg.com/@ugdu/runtime/dist/index.js"></script>
  </head>
  <body>
    <div id="app"></div>
  </body>
</html>

Create and run task

Below is our task script.

import { argv } from 'process'

/**
 * @ugdu/packer is powered by vite. So we can use vite plugin.
 */
import vue from '@vitejs/plugin-vue'
import { Processor } from '@ugdu/processor'
/**
 * `serve` and `build` are `task options` which is used to create `task`.
 * `serve` is used to start a dev server.
 * `build` is used to build for production.
 */
import { serve, build } from '@ugdu/packer'

const task = new Processor().task(argv[2] === 'serve' ? serve : build)

task.hook(
  'get-config',
  // The return value of this function will be seemed as config.
  () => {
    return {
      extensions: ['vue', 'ts', 'js'],
      apps: [
        {
          name: '@xx/container',
          packages (lps) {
            return lps.map((lp) => lp.name)
          }
        }
      ],
      meta: 'local',
      vite: {
        plugins: [vue()]
      }
    }
  }
)

task.run()

This command will build the project for production and launch a server to preview the production build.

node scripts/task.js
pnpm vite preview

This command will start a dev server.

node scripts/task.js serve

Terms

  • task options A definition of a task.
  • task A task is an instance of Task which is a subclass of HookDriver.
  • vendor package The package you installed in your node_modules.
  • module In general, a generated js file is a module. For more detail, check here.
  • local module The module comes from local package.
  • binding The variable the module import and export.