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

arcadia-main

v0.0.1-f001a1

Published

This is the main module of the arcadia framework. It gives you good API to write providers, plugins and deployers.

Downloads

6

Readme

arcadia-main

This is the main module of the arcadia framework. It gives you good API to write providers, plugins and deployers.

Providers

Providers give you collection of methods, properties to work with you application. For example, the DatabaseProvider gives you abstract migration system. But using this one you cannot work any database. You need a low-level provider e.g. driver.

Drivers

After we have abstract providers we need to get access to something, so we use drivers. Driver is a low-level module, though, usually it's default TypeScript file, that work with the database subset.

For example, if you're going to use sqlite3, you'll need to have DatabaseProvider, SQLite3DatabsaseProvider, SQLite3Driver, and the sqlite3 npm package. So, totally we have 3 files and one package. Why so hard to do that?

Reason of using providers and drivers ins't as hard as it looks now. Trully you describe API in the driver and some request api methods in provider. It's really easy.

Configuration

Every module, provider, driver will need some configuration. There's special collection of classes for configuration.

ConfigCollection. This is the directory handler.

Examples

ConfigCollector. This is the config file handler. The class let you to manipulate info written to the config file, read and query it.

NOT DONE YET Now it doesn't support write in file.

Examples