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

@nxn/boot

v1.0.91

Published

boot framework, config based and services, application components, API/routes, middleware, code gen.

Downloads

15

Readme

Tutorial : using nxn-boot

NB. DO NOT INSTALL THIS GIT PACKAGE ON YOUR PC. Unless you need to modify the framework itself, there is no need to install the git project. You'll see below how to use it from npm.

Overview

NXN is a framework for small to large scale applications, supporting configuration file, services, routes, express middleware, client data.

Small to very large applications, battle tested.

The main difference with other node.js frameworks are :

Framework

  • pure javascript based,
  • all components are simple classes : no heavy library to learn. Only one class to derive from (optional)
  • injections of components for modular architecture,
  • each component benefits from its own configuration (parameters)
  • all services, routes, models etc. are described in a YAML config (also generated with the CLI)

Medium code

  • message/ node based architecure can be used for data processing chains (ex. indexing for AI, or other jobs)
  • generation of 80% of the code : you just have to write code for your business logic

Quality and documentation

  • jsdoc based with type checking enabled by default : benefit from types and ts typs without compiling
  • documentation of the project generated in mermaid format.

Base components for creating REST API

  • Routes : for creating REST controllers,
  • Services : for doing actual work ("providers"),

Routes and services are simple classes with optional "init()" functions. These classes are listed in a YAML file and loaded by nxn at boot time.

see sample below...

Install

Install @nxn/boot cli nxg from npm:

npm install -g @nxn/cli

init the project:

nxg init

and install dependencies:

npm install

This creates following file structure:

Basically: index.js loads the application config_default.yml and initialises all components. Then it runs express (default server here).

##Run the generated sample:##

Run the sample:

node index.js

or

npm start

You should then see :

The application is then up and running.. It doesnt do much right now but everything is ready. Have a look on the config file and you'll see sections where routes, services, run, tests anf middleware will be listed.

Docker

Just to make sure Dowker is also ready to go, create the image and run it:

npm run docker
npm run docker:run

You should then see the image running as well if Docker is installed on your workstation.

NEXT >> Sample