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

require.mjs

v0.0.0

Published

Require local JSON files in files utilizing the `.mjs` experimental module system

Downloads

3

Readme

require.mjs

Require local JSON files in files utilizing the Node.js v8.5.0 .mjs/--experimental module system

Note: to get this functionality, please use this snippet.

Why not a module?

As I was working to get this functionality in place, I was running into issues with the lack of metavariables like __dirname (as referenced here) that would prove useful for use with path.resolve and fs.readFileSync.

The issue I was coming across was that the function would attempt to look for a file relative to wherever the function was declared. In my module, using index.mjs as a module imported into __tests__/requireDataJson.mjs would look for the required JSON file, data.json, at the project root (as a sibling of index.mjs); in a published package, this would result in the require() function looking in path/to/node_modules/require.mjs/dist/. (I've set the main property in the package to /dist/index.mjs)

If you think you can fix this issue, please feel free to file a Pull Request, or to discuss this further, file an Issue.

Contributing

Please fork this repo, and work under a branch titled fork.

Installing Dependencies

This project uses Yarn to manage dependencies. (More info here)

Run $ yarn to install dependencies.

Building

For development, run $ yarn run babel to build to /dist

For release, run $ yarn run build to check Flow types, run Prettier over files, and strips Flow types and minifies the code using Babel.

Other scripts

Run Flow to check type annotations:
$ yarn run flow

Run Prettier to auto-format .js, .mjs, and .json files:
$ yarn run prettier

License

MIT