Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2024 – Pkg Stats / Ryan Hefner

@hwbdev/exports

v1.0.2

Published

2 years ago

This package demonstrates the exports field in package.json. There are two ways to specify entry points to a package: the 'main' and 'exports' field.

Downloads

13

0High
0Medium
0Low

This package demonstrates the exports field in package.json. There are two ways to specify entry points to a package: the 'main' and 'exports' field.

'exports' map a name to a path, so that whenever that name is imported, the file at the specified path is used. 'exports' prevents external packages from importing any files that are not specified in 'exports'.
'main' specifies the file to import when the name of the package is specified (as opposed to a file within the package).

'exports' takes precedence of 'main'.

For example, if an external package has var mod = require('@hwbdev/exports'), entrypoint1.js will actually run. If 'exports' wasn't defined, main.js will be the one that runs. Where as if the external package has var mod = require('@hwbdev/exports/entrypoint1'), main.js will be the one that runs. If 'exports' wasn't defined, entrypoint1.js will be the one that runs. If the external package has var mod = require('@hwbdev/exports/unaccessible'), an error will show up. If 'exports' wasn't defined, unaccessible.js will run.