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

@ram-stack/import-replacer-helper

v1.0.1

Published

A helper to create import replacing macros

Downloads

10

Readme

Import replacer helper

This package provides a helper for creating Babel macros that expand namespace imports into direct imports. It is useful for consuming libraries like Material-UI which bundle a large number of standalone modules.

For these libraries using a namespace import (import * as MUI from '@material-ui/core') compromises build performance and bundle size (see tree-shaking).

A macro such as @ram-stack/material-ui.macro prevents above mentioned issues by replacing namespace import with only a necessary subset of direct imports. Doing that proactively helps the compiler and bundler to exclude unused code and avoid extra work.

Installation

This module is distributed via npm which is bundled with node and should be installed as one of your project's dependencies:

npm install --save @ram-stack/import-replacer-helper

Usage

import-replacer-helper API consists of a single function: createReplacerMacro. createReplacerMacro takes replacer function getPath and preferred default namespace import statement defaultNamespaceImport and returns an instance of a macro that can be exported and consumed by babel-plugin-macros.

Example

const {createReplacerMacro} = require('@ram-stack/import-replacer-helper');
const {name: packageName} = require('./package');

module.exports = createReplacerMacro({
  getPath: name => `@material-ui/core/${name}`,
  defaultNamespaceImport: `import MUI from '${packageName}'`,
});

TypeScript usage

If a package targeted by the macro provides TypeScript type definitions it is recommended to reexport those definitions from the macro package itself. In order to achieve this, a typings file should be created. For example, macro.d.ts:

/* macro.d.ts */
export * from '@material-ui/core';
export {default} from '@material-ui/core';

Then it has to be referenced in package.json:

+  "types": "macro.d.ts",

See also

@ram-stack/material-ui.macro @ram-stack/material-ui-cons.macro

babel-plugin-macros

License

MIT