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

to-factory

v1.0.0

Published

Convert classes into factory functions so they can be called with or without new.

Downloads

157,737

Readme

to-factory

Convert classes into factory functions.

Allows ES6 classes to be instantiated with or without new.

Allows your API consumers to not need to divine (there's no built-in way to know) which functions you intend to be called with new, and which functions are to be called without.

Example

without to-factory

Must call a class with new, cannot call class as a function:

class Person {
  constructor(name) {
    this.name = name
  }
}

new Person('alice') // ok
Person('bob') // TypeError: Cannot call a class as a function

with to-factory

Call a class with new or as a function:

// exact same Person class as above example

Person = toFactory(Person)

const personA = new Person('created with new')
console.log(personA.name) // => 'created with new'

const personB = Person('created without new')
console.log(personB.name) // => 'created without new'

Inheritance, etc all works as expected

// Inheritance works as expected
class BigPerson extends Person {
  constructor(name) {
    super(name.toUpperCase())
  }
})

BigPerson = toFactory(BigPerson)

const bigPersonA = new BigPerson('created with new')
console.log(bigPersonA.name) // => 'CREATED WITH NEW'

const bigPersonB = BigPerson('created without new')
console.log(bigPersonB.name) // => 'CREATED WITHOUT NEW'

Why

The "can't call without new" restriction on ES6 classes create a needless incompatibility between tools which accept classes and tools which accept regular functions – there is no built-in means for a tol to determine whether a function wants be called with new or without new, it just has to pick one and hope for the best.

While it's true that some real-world functions insist on being constructors in much the same way, at least it is possible to patch the library and/or submit a pull request explaining that requiring new is uneccessarily rigid and provides little benefit when it's entirely possible to transparently handle both cases. With ES6 classes we have no option to just patch the library as this rigidity is baked right into the implementation.

See Also

License

MIT