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

angular-monorepo-packages-test

v0.0.0

Published

This repository exists to demonstrate setting up Lerna and providing contribution guidelines for projects using Lerna.

Downloads

3

Readme

Angular Monorepo Packages Test

This repository exists to demonstrate setting up Lerna and providing contribution guidelines for projects using Lerna.

  1. Setup Lerna
  2. Contributing Guidelines

Important links:

1. Setup with Lerna

For more information on Lerna, read up on their source repo docs: https://github.com/lerna/lerna

  1. Setup with Lerna
    1. Init Lerna
    2. Modify lerna.json
    3. Modify package.json
    4. Modify each project's package.json
    5. Modify each project's ng-package.json/ng-package.prod.json

1.i. Init Lerna

Run npx lerna init within the main project directory (not 'projects').

1.ii. Modify lerna.json

Use the following for the lerna.json file. These configurations can be modified as needed.

{
  "packages": [
    "projects/*"
  ],
  "command": {
    "publish": {
      "contents": "dist",
      "conventional-commits": true
    },
    "version": {
      "message": "chore(release): publish %s",
      "conventional-commits": true,
      "push": false
    },
    "bootstrap": {
      "npmClientArgs": ["--no-package-lock"]
    }
  },
  "version": "independent"
}

1.iii. Modify package.json

Add the following scripts to the package.json

"lerna-version": "lerna version --yes --conventional-commits",

"postversion": "lerna run build",

The following are unnecessary within TFS/Azure DevOps at present:

"lerna-publish": "lerna publish --yes --conventional-commits",

"prepublish": "lerna run build",

1.iv. Modify each project's package.json

Modify name for scope

If using scoping for the project names, change the name to include the scope:

Before: "name": "my-project"

After: "name": "@my-scope/my-project"

Add build script

Add the following script to the package.json

{
    ...
    "scripts": {
        "build": "ng build my-project --prod"
    },
    ...
}

1.v. Modify each project's ng-package.json/ng-package.prod.json

Modify the dest property in ng-package.json and ng-package.prod.json to

{
    "dest": "./dist",
    ...
}

2. Contributing Guidelines

For more details on the git commit guidelines and their source, check out: https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines