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

@heisian/quire

v1.0.1

Published

Javascript needs more modern!

Downloads

5

Readme

Quire

Welcome to the future, where less is cool.

What is Quire?

Quire gets rid of the 're' in 'require.' What do you get out of Quire?

  • Less typing.
  • Convenient namespacing in deeply nested paths.
  • Avoid eslint's global-require rule altogether. Your code isn't crappy if you can abstract away the inconsistencies!

OK, I'm fully convinced. How do I use it???

Suppose you have a not-so-deeply nested file somewhere:

// path/shared/someModule.js
module.exports = () => 'Hello, dude!'

Let's say you also have a couple other modules in the same folder, anotherModule and yetAnotherModule.

Now, in a much more deeply nested file, Quire makes including the aforementioned modules a breeze! Check it:

// path/to/my/thingy/index.js
const Quire = require('quire')
const quire = new Quire('path/shared') // Easy to read, relative to root

const someModule = quire('someModule') // Nothin' but the module name, baby
const anotherModule = quire('anotherModule') // You know you like it, don't deny
const yetAnotherModule = quire('subpath/yetAnotherModule') // Aww yea, this rox!

// Look ma, no ../'s!

process.stdout.write((someModule()) // Outputs 'Hello, dude!'

So modern! So... wait.. why are you using CommonJS?

Until the war of "Michael Jackson script," dynamic imports, et. al, is won, we're stuck with one foot in the present, and one foot in the future. Which technically puts you in the future. So be happy.

P.S., have you heard about ES9 yet?


You know this software is legit coz it's got this crazy license block, yo.
Copyright (C) 2018 Timothy Huang

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.