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

plugin-importmap

v0.0.1-alpha.0

Published

## Install `npm i plugin-importmap`

Downloads

3

Readme

Architect importmap plugin

Install

npm i plugin-importmap

Usage

Add importmap to the @plugins pragma in your app.arc file.

@plugins
importmap

Add an @importmap pragma to your app.arc file and declare the name and filepath of the files you want to make available to the browser.

@importmap
hello src/shared/hello.mjs

This will expose the hello.mjs file inside your handler at: import { hello } from '@architect/importmap/hello.mjs'

The files will be bundled, fingerprinted and exposed in a map for sending to the browser here: import map from '@architect/importmap/browser/index.mjs'

In the format:

export default {
  "hello": "/_importmap/hello-c63b938.mjs",
}

where the path is to the bundled and fingerprinted file.

Import the hello file in the browser <script src="/_importmap/hello-c63b938.mjs" type="module"></script>