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

shared-sidemenu

v0.1.4

Published

### Steps to Integrate sidemenu into application Step 1: Install the [shelljs](https://www.npmjs.com/package/shelljs) library

Downloads

6

Readme

shared-sidemenu

Version - 0.1.4

Steps to Integrate sidemenu into application

Step 1: Install the shelljs library

Step 2: Copy the setup-sidemenu.js file to application root folder

Step 3: Add line of code postinstall to package.json

 "scripts": {
    "ng": "ng",
    --> "postinstall": "node ./setup-sidemenu.js",
        "start": "ng serve",
        "build": "ng build",
        "test": "ng test",
        "lint": "ng lint",
        "e2e": "ng e2e"
    },
    
   "dependencies": {
     --> "shared-sidemenu": "^0.1.4",
     "@angular/common": "^4.0.0",

Step 4: Configured sidemenu in app.module.ts file

    import { SideMenuModule } from 'shared-sidemenu';
        
    imports: {
    -->  SideMenuModule.forRoot()
    }

Step 5: Add the Component Code in HTML file

    <left-side-menu-select [styles]="styles" [type]="'normal'"
                               [assetsPath]="''" [isVarianceNavigation]="true"
                               [isOpen]=false [loadURL]="SIDE_MENU_URL" [position]="''">
    </left-side-menu-select>

Sample values for SIDE_MENU_URL: 'http://52.38.158.252:7270/ttsm/api/ttsmconfig?param=side_menu' and styles={top: '2px', position: 'absolute'},

Ignore the sideMenuAssetsPath, position input values. (Not required at this moment)

Installing updates

Step 1: Version Changes in package.json

 "dependencies": {
   --> "shared-sidemenu": "^0.1.2",
   "@angular/common": "^4.0.0",

Step 2: Run from CLI

$ npm install

Library Development

To generate all *.js, *.d.ts and *.metadata.json files:

$ npm run build

to automatically create all *.js, *.d.ts and *.metadata.json files in the dist directory:

dist
├── index.d.ts                  # Typings for AOT compilation
├── index.js                    # Flat ES Module (FESM) for use with webpack
├── lib.d.ts                    # Typings for AOT compilation
├── lib.metadata.json           # Metadata for AOT compilation
├── lib.umd.js                  # UMD bundle for use with Node.js, SystemJS or script tag
├── package.json                # package.json for consumer of your library
├── sample.component.d.ts       # Typings for AOT compilation
├── sample.directive.d.ts       # Typings for AOT compilation
├── sample.pipe.d.ts            # Typings for AOT compilation
└── sample.service.d.ts         # Typings for AOT compilation

Finally you publish your library to NPM by publishing the contents of the dist directory:

$ npm publish dist

To lint all *.ts files:

$ npm run lint

Live Preview changes

$ cd demo 
$ nf start 

Publishing your library to NPM

To publish your library to NPM, first generate the dist directory:

$ npm run build

and then publish the contents of the dist directory to NPM:

$ npm publish dist

License

MIT © durga