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

@kaltura-ng/dev-workspace

v2.4.1

Published

Kaltura internal tool used to setup Kaltura applications development workspace

Downloads

4

Readme

Kaltura Dev Workspace

Gitter chat npm version

Tool for managing JavaScript projects with multiple packages.

About

Our code base for kmc-ng and tvm-ng is organized into multiple packages/repositories. However, making changes across many repositories is messy.

For monorepos there is a great tool named lerna that optimizes the workflow around managing multi-package repositories with git and npm.

But in our case with have a mix of:

  • single package repo.
  • single application repo.
  • multiple packages in monorepo.

Unfortunately lerna only support monorepo so we cannot use it as-is.

To overcome this issue we created this tool.

Kaltura dev workspace package is inspired deeply from lerna tool. We find lerna the best tool that simplify complicated dev-op operation. We recommend you to try lerna for your own projects.

Who should use this tool

This tool was created for Kaltura applications development and is not suppose to be used for other projects.

Getting Started

Prerequisites

  • [x] Ensure you have node.js installed, version 7.0.0 or above.
  • [x] Ensure you have git installed
  • [x] Ensure you have npm installed, version 5.0.0 or above.

Setup your workspace

  1. create a folder to hold your packages (your workspace root folder).
  2. create package.json in your root folder by running the following command:
 $ npm init -y
  1. add this tool to your folder in your root folder by running the following command:
$ npm install @kaltura-ng/dev-workspace
  1. create file kaltura-ws.json in your root folder with the following format:
 {
   "version" : "2.0.0",
   "repositories": [
     { "origin" : "github", "uri": "https://github.com/kaltura/kaltura-ng.git"},
     { "origin" : "github", "uri": "https://github.com/kaltura/kaltura-ng-mc-theme.git"},
     { "origin" : "github", "uri": "https://github.com/kaltura/kmc-ng.git"}
   ],
   "licenses" : {
     "ignoreList" : [      
       "kaltura-typescript-client"
     ]
   }
 }

Notes:

  • you should modify repositories property to hold a list of relevant repositories to your kaltura project ordering them by the dependency constraints.
  • the sample above will setup your workspace to develop kmc-ng application.
  1. add the following to your package.json:
{  
  "scripts" : {
    "kws" : "kws",
    "setup" : "kws setup",
    "build" : "kws run build",
    "licenses" : "kws licenses",
    "clean" : "kws clean"
  }
}
  1. run setup command to build & symlink your repositories
$ npm run setup

Commands

init

setup

run

licenses

clean