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

@bagubagu/schematics

v0.3.30

Published

Bagubagu Schematics

Downloads

69

Readme

Bagubagu Schematics

Develop

First thing first

npm install -g schematics-cli
git clone https://github.com/bagubagu/s.git
yarn install
yarn build

Modify table component

Modify src/table/files/*

to test:

# Test from an example angular project
cd example

# this will not really create the files
# because it's running in dry-run mode
schematics ..:table

# to see the changes
schematics ..:table --dry-run=false

Create new component

  1. Add your new component to src/collection.json
  2. mkdir src/newcomponent
  3. create your new component, use src/table as example

To test the component

cd example

# this will run in dry-run mode (not changing anything)
schematics ..:mycomponent

# set dry-run to false, to see changes
schematics ..:mycomponent --dry-run=false

Test from an existing angular project

# link our schematics to global
cd s
npm link .

# test from hijrah-admin
cd ../hijrah-admin
npm link @bagubagu/schematics
ng g @bagubagu/schematics:table

How to use

npm i -g @bagubagu/schematics

Create .json for @bagubagu/schematics

cd ./angular_project/src/app/
generate-json-schematics

This will generate <file_name>.json in ./angular_project/src/app

Create new table

 ng g @bagubagu/schematics:table <table_name> --project=<project_name>

Note: Before creating a new table please make sure that <table_name>.json's path is included (and/or) <table_name>.json does exists

Create new Service

 
 # this will run in dry-run mode (not changing anything)
 ng g @bagubagu/schematics:service <service_name> --project=<project_name>

Create new Pipe


  ng g @bagubagu/schematics:pipe <pipe_name> --project=<project_name>

Example

Create Table

  cd ./project/hehe/product/
  generate-json-schematics 
? What do you want to create?  (Use arrow keys)
  Form
❯ Table

  ng g @bagubagu/schematics:table product/product-list --dry-run=false

Create Form

  cd example/src/app/product/
  generate-json-schematics 
? What do you want to create?  (Use arrow keys)
❯ Form
  Table
  cd example/
  ng g @bagubagu/schematics:form product/product-add --dry-run=false

Service

   cd example/
   ng g @bagubagu/schematics:service product/product --project=example --dry-run=false

Pipe

  cd example/
  ng g @bagubagu/schematics:pipe product --project=example --dry-run=false