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

pkg.macro

v1.0.1

Published

Fetch properties of your project's `package.json` at compile time.

Downloads

7

Readme

pkg.macro · Version License JavaScript Standard Style

Fetch properties of your project's package.json at compile time.

pkg.macro allows you to turn pkg(["name", "version"]) into { name: "your-package", version: "1.0.0" } as a build time constant.

installation

yarn add --dev pkg.macro

Make sure you also have [Babel][babel] and [babel-plugin-macros][babel-plugin-macros] installed:

yarn add --dev @babel/cli @babel/core babel-plugin-macros

... and configured with Babel:

module.exports = {
  presets: [],
  plugins: ["babel-plugin-macros"]
}

usage

import pkg from "pkg.macro"

const props = pkg([
  "name",
  "version",
  "scripts.test",
  ["dependencies", "some-package"]
])

The above is transformed to:

const props = {
  name: "your-package",
  version: "1.0.0",
  scripts: {
    test: "test-script"
  },
  dependencies: {
    "some-package": "1.0.0"
  }
}

see also

  • param.macro – macro for partial application, inspired by Scala's _ & Kotlin's it

development

  1. Clone the repo: git clone https://github.com/citycide/pkg.macro.git
  2. Move into the new directory: cd pkg.macro
  3. Install dependencies: yarn or npm install
  4. Build the source: yarn build or npm run build
  5. Run tests: yarn test or npm test

contributing

Pull requests and any issues found are always welcome.

  1. Fork the project, and preferably create a branch named something like feat-make-better
  2. Follow the build steps above but using your forked repo
  3. Modify the source files in the src directory as needed
  4. Make sure all tests continue to pass, and it never hurts to have more tests
  5. Push & pull request! :tada:

license

MIT © Bo Lingen / citycide