Socket
Socket
Sign inDemoInstall

@lerna/project

Package Overview
Dependencies
66
Maintainers
4
Versions
76
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    @lerna/project

Lerna project configuration


Version published
Weekly downloads
513K
decreased by-4.37%
Maintainers
4
Created
Weekly downloads
 

Changelog

Source

3.0.0-beta.12 (2018-03-30)

Bug Fixes

  • create: Silently ignore missing builtin npmrc (1523520), closes #1353
  • npm-conf: Replace env vars even in config keys (3c9a5de)

Features

  • package: Add serialize() method (fdec3ac)
  • package: Add Map-like get/set methods, remove raw json getter (707d1f0)
  • project: Merge package and packageJson into manifest (9a47ff7)
  • Add --no-prefix for streaming output (#1352) (36c1fad)

BREAKING CHANGES

  • package: The Package class no longer provides direct access to the JSON object used to construct the instance. Map-like get()/set(val) methods are available to modify the internal representation.

<a name="3.0.0-beta.11"></a>

Readme

Source

@lerna/project

Lerna project configuration

Configuration Resolution

Lerna's file-based configuration is located in lerna.json or the lerna property of package.json. Wherever this configuration is found is considered the "root" of the lerna-managed multi-package repository. A minimum-viable configuration only needs a version property; the following examples are equivalent:

{
  "version": "1.2.3"
}
{
  "name": "my-monorepo",
  "version": "0.0.0-root",
  "private": true,
  "lerna": {
    "version": "1.2.3"
  }
}

Any other properties on this configuration object will be used as defaults for CLI options of all lerna subcommands. That is to say, CLI options always override values found in configuration files (a standard practice for CLI applications).

Command-Specific Configuration

To focus configuration on a particular subcommand, use the command subtree. Each subproperty of command corresponds to a lerna subcommand (publish, create, run, exec, etc).

{
  "version": "1.2.3",
  "command": {
    "publish": {
      "loglevel": "verbose"
    }
  },
  "loglevel": "success"
}

In the example above, lerna publish will act as if --loglevel verbose was passed. All other subcommands will receive the equivalent of --loglevel success (much much quieter).

Keywords

FAQs

Last updated on 30 Mar 2018

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc