Socket
Socket
Sign inDemoInstall

@lerna/filter-options

Package Overview
Dependencies
71
Maintainers
4
Versions
80
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    @lerna/filter-options

Options for lerna sub-commands that need filtering


Version published
Weekly downloads
482K
increased by0.54%
Maintainers
4
Install size
848 kB
Created
Weekly downloads
 

Changelog

Source

3.1.2 (2018-08-20)

Bug Fixes

  • Setup instance.filteredPackages explicitly (32357f8)
  • Use packageGraph.rawPackageList instead of misleading instance.filteredPackages (2e2abdc)
  • bootstrap: Remove redundant duplicate name check (c2405a1)
  • command: Remove redundant filteredPackages calculation (e0a361f)
  • filter-options: Move filterPackages logic into named export (e863c28)
  • package-graph: Throw errors when package names are not unique (387df2b)
  • publish: Allow composed version command to decide when to verify working tree (e61aa67)

<a name="3.1.1"></a>

Readme

Source

@lerna/filter-options

Options for lerna sub-commands that need filtering

Options

--scope <glob>

Include only packages with names matching the given glob.

$ lerna exec --scope my-component -- ls -la
$ lerna run --scope toolbar-* test

--ignore <glob>

Exclude packages with names matching the given glob.

--no-private

Exclude private packages. They are included by default.

--since [ref]

Only include packages that have been updated since the specified ref. If no ref is passed, it defaults to the most-recent tag.

# List the contents of packages that have changed since the latest tag
$ lerna exec --since -- ls -la

# Run the tests for all packages that have changed since `master`
$ lerna run test --since master

# List all packages that have changed since `some-branch`
$ lerna ls --since some-branch

This can be particularly useful when used in CI, if you can obtain the target branch a PR will be going into, because you can use that as the ref to the --since option. This works well for PRs going into master as well as feature branches.

--include-filtered-dependents

Include all transitive dependents when running a command regardless of --scope, --ignore, or --since.

--include-filtered-dependencies

Include all transitive dependencies when running a command regardless of --scope, --ignore, or --since.

Used in combination with any command that accepts --scope (bootstrap, clean, ls, run, exec). Ensures that all dependencies (and dev dependencies) of any scoped packages (either through --scope or --ignore) are operated on as well.

Note: This will override the --scope and --ignore flags.

i.e. A package matched by the --ignore flag will still be bootstrapped if it is depended on by another package that is being bootstrapped.

This is useful for situations where you want to "set up" a single package that relies on other packages being set up.

$ lerna bootstrap --scope my-component --include-filtered-dependencies
# my-component and all of its dependencies will be bootstrapped
$ lerna bootstrap --scope "package-*" --ignore "package-util-*" --include-filtered-dependencies
# all packages matching "package-util-*" will be ignored unless they are
# depended upon by a package whose name matches "package-*"

Keywords

FAQs

Last updated on 20 Aug 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