dependency-tree - npm Package Compare versions

Comparing version 6.4.1 to 6.5.0

bin/cli.js

		@@ -14,2 +14,3 @@ #!/usr/bin/env node
		.option('-w, --webpack-config <path>', 'path to a webpack config')
		.option('-t, --ts-config <path>', 'path to a typescript config')
		.option('--list-form', 'output the list form of the tree (one element per line)')
		@@ -24,3 +25,4 @@ .parse(process.argv);
		config: program.requireConfig,
		webpackConfig: program.webpackConfig
		webpackConfig: program.webpackConfig,
		tsConfig: program.tsConfig
		};
		@@ -27,0 +29,0 @@

package.json

		{
		"name": "dependency-tree",
		"version": "6.4.1",
		"version": "6.5.0",
		"description": "Get the dependency tree of a module",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -110,3 +110,3 @@ ### dependency-tree [![npm](http://img.shields.io/npm/v/dependency-tree.svg)](https://npmjs.org/package/dependency-tree) [![npm](http://img.shields.io/npm/dm/dependency-tree.svg)](https://npmjs.org/package/dependency-tree)

		If there are bugs in [precinct](https://github.com/dependents/node-precinct) or if the `requireConfig`/`webpackConfig` options are incomplete,
		If there are bugs in [precinct](https://github.com/dependents/node-precinct) or if the `requireConfig`/`webpackConfig`/`tsConfig` options are incomplete,
		some dependencies may not be resolved. The optional array passed to the `nonExistent` option will be populated with paths
		@@ -113,0 +113,0 @@ that could not be resolved. You can check this array to see where problems might exist.

New alerts