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

midgard-schematics

v1.2.1

Published

CLI tool for assembling a Walhall app based on Midgard and other modules

Readme

Midgard-schematics

Midgard-schematics is an npm package that uses @angular-devkit/schematics and gulp.js to clone the repositories of all the frontend clients in a Walhall application and auto-generate the necessary code to build a single UI.

Usage

The Walhall application will run the schematics gulp commands when it initializes (npm run init), utilizing midgard-schematics as a dev-dependency.

To use this package for local development, you need to install gulp-cli globally.

The gulp command looks like this:

gulp <taskname> --gulpfile node_modules/midgard-schematics/lib/gulpfile.js [--cwd optional_custom_execution_path]

Example:

gulp schematics --gulpfile node_modules/midgard-schematics/lib/gulpfile.js

The gulp task will clone the application's frontend clients to the projects folder in your application root, install each client as an npm package, and make the following configuration modifications:

  1. tsconfig.json: Add the client's paths to the paths object.
  2. angular.json: Add the Angular configurations of the imported client.
  3. src/tsconfig.app.json: Include the client's TypeScript files in the application's TypeScript compilation.
  4. projects/midgard-angular/src/lib/midgard-routing.module.ts: Add the client's routes to the Midgard-Angular routing component.
  5. projects/midgard-angular/src/lib/modules/store/store.ts: Add the reducers and the epics to the Midgard-Angular Redux store.
  6. [DOM]: Add exit point component to the DOM depending on the exitPointComponent defined in the Walhall application's configuration.

Available schematics rules

The aforementioned configuration modifications are carried out according to different schematics rules that can be found under src/utils:

  1. updateTsConfigRule(options): Updates tsconfig.json.
  2. addLibraryToWorkspaceFileRule(options): Updates angular.json.
  3. updateAppTsConfigRule(options): Updates src/tsconfig.app.json.
  4. addRouteRule(options): Responsible for adding routes to midgard-routing.module.ts.
  5. addAddReducersAndEpicsRule(options): Responsible for adding epics and reducers to the Redux store.
  6. addExitPointRule(options): Responsible for adding an exitPoint element to the DOM.