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

ansofra

v1.0.4

Published

Ansofra Framework by Newdich Technology - build software fast. Run: npx ansofra new myapp

Readme

ANSOFRA FRAMEWORK - BY NEWDICH TECHNOLOGY

This is the TypeScript/Node.js version of the Ansofra framework. It follows the exact same structure, naming and philosophy as the PHP version, so if you know one, you know both.

FOLDER STRUCTURE (same as the PHP version)

ansofra/ -> the entering point + the public folder (the only folder that should be exposed in production) index.ts -> THE ENTERING POINT (was ansofra/index.php) public/ -> static files: css, js, images, uploads, swagger, 404 route/ -> route/index.ts: register every endpoint here Controller/ -> thin controllers App/ -> controllers of the USERS AREA (/api/...) Src/ -> controllers of the ADMINS AREA (/apiadmin/...) app/ -> business logic of the USERS AREA Command/ -> logic that WRITES data (register, update...) Query/ -> logic that READS data (login, get...) src/ -> business logic of the ADMINS AREA Command/ -> admin logic that WRITES data Query/ -> admin logic that READS data Schema/ -> database layer Settings.ts -> exposes every .env value (was Settings.php) Platform.ts -> YOUR TABLES are designed here (was Platform.php) Dealer.ts -> MySQL connections (was Dealer.php) Migration.ts -> the mini-ORM: save, getSpecific, edit, remove... RunMigration.ts -> auto creates all tables in Platform.ts Dto/ -> AnsofraDto.ts: every incoming request is wrapped here Middleware/ -> Index.ts: getIp, hashData, verifyHash, cleanData, otp... Auth/ -> Authentication.ts (login -> JWT cookie) Authorization.ts (verify JWT cookie) Cache/ -> Redis caching + RateLimit Mail/ -> Index.ts (SMTP/nodemailer), Sendgrid.ts, Mailgun.ts, Mailersend.ts Files/ -> Upload.ts, Download.ts apis/ -> third-party API integrations (CurrencyConverter...) bootstrap.ts -> loads .env (was boostrap.php) ansofra-generator.ts-> generates swagger docs (was ansofra-generator.sh)

HOW TO START

  1. npm install
  2. cp .env.example .env (then edit the values)
  3. npm run migrate (creates your database tables)
  4. npm run dev (starts the server: http://localhost:8080)

HOW TO BUILD FOR PRODUCTION

  1. npm run build (compiles TypeScript into dist/)
  2. npm start (runs the compiled server)

HOW TO GENERATE API DOCUMENTATION

npm run ansofra-generator (writes the swagger json files into ansofra/public/swagger/) Then open http://localhost:8080/api to view the docs.

NOTES

  • Don't forget to change the values in the .env to meet your data.
  • In production only expose ansofra/public as static; keep .env safe.
  • The flow of every request is always: route -> Controller -> Dto -> app|src (Command/Query) -> Schema/Migration -> response