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

@padcom/vite-plugin-federation

v0.0.10

Published

Vite federation plugin automatic configurator

Downloads

6

Readme

@padcom/vite-plugin-federation

This is a configuration plugin for @originjs/vite-plugin-federation. It allows, instead of crafting the configuration each time manually, to get it configured with data from package.json.

Installation

To install the package issue the following command:

$ npm install --save-dev @padcom/vite-plugin-federation

Configuration

Once the plugin is installed you need to let Vite know you want to use it:

vite.config.js:

import { defineConfig } from 'vite'
import federation from '@padcom/vite-plugin-federation'

export default defineConfig({
  build: {
    target: 'esnext',
  },
  plugins: [
    federation(),
  ],
})

That's it! No more manual federation configuration!

What's in the box?

Once you install this plugin the following will happen:

  1. The name of the exposed package will come from either the package.json/name or from package.json/federation/name.
  2. Shared dependencies will be loaded from package.json/dependencies
  3. If there is no remotes section in package.json/federation then the exposed elements will be either package.json/federation/exposes or
{
  './root': './src/index.js'
}
  1. If package.json/remotes is set then there are no automatic exposes and whatever is added to package.json/exposes will be forwarded to the underlying plugin.

So if you're creating a federated module and you just want to expose everything all at once then create a file ./src/index.js in your project, export all your elements from that file and you're all set.

Importing exposed elements

Once your library is ready you can import it in another project like so:

const library = await import('libraryName/root')
const root = library.default

Configuring for different environments

To tell the federation plugin where the right version of the library is we can use the mode switch from vite. The plugin uses dotenv and if the content of the location of the remote is found in environment variables then it is automatically substituted with the value of that env variable from .env file in your project's root folder:

LIBRARY_URL=http://localhost:5001/assets/remoteEntry.js

and then use it in package.json

{
  "federation": {
    "remotes": {
      "library": "LIBRARY_URL"
    }
  }
}

If you want to provide a differenty URL for production create the .env.production file with the following content:

LIBRARY_URL=https://somewhere.on-the-internet.net/assets/remoteEntry.js