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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@loyaltylion/typeorm

v0.2.29-4

Published

loyaltylion fork

Downloads

25

Readme

@loyaltylion/typeorm

How to make changes to our fork:

  • use the loyaltylion/changes branch
    • while you're making changes, consider rebasing it on the latest typeorm master
  • make your changes -- keep everything organised with good, isolated commits in case we want to cherry pick some of these commits to get them upstream later
  • install dependencies
    • some dependencies will not install when running on ARM, so we run it on a linux/amd64 container instead
    • run docker run -it --platform linux/amd64 -v ${PWD}:/app -w /app node:12 npm install
  • to test it locally:
    • run yarn package
    • this will create a dist build in build/package
    • from inside build/package, run yarn link
    • inside projects using this fork, run yarn link "@loyaltylion/typeorm". this will link it to your local build
    • each time you make a change in the fork you'll need to run npx gulp package in there again
  • to publish:
    • adjust the package.json version from x.x.x-y to x.x.x-z (z = y + 1)
    • run npx gulp publish. this will publish a new version to @loyaltylion/typeorm
    • update referenced projects to use the new version from NPM: yarn upgrade --latest @loyaltylion/typeorm