Comparing version 1.0.2 to 1.0.3
@@ -231,2 +231,4 @@ var progressBar = require("../progress-bar"); | ||
console.log(chalk.green("Successfully published " + NEW_VERSION + ".")); | ||
console.log("Updated Packages"); | ||
console.log(changedPackages); | ||
process.exit(); | ||
@@ -233,0 +235,0 @@ }); |
{ | ||
"name": "lerna", | ||
"version": "1.0.2", | ||
"version": "1.0.3", | ||
"description": "Tool for managing JavaScript projects with multiple packages", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -6,3 +6,3 @@ <p align="center"> | ||
<p align="center"> | ||
Tool for managing JavaScript projects with multiple packages. | ||
A tool for managing JavaScript projects with multiple packages. | ||
</p> | ||
@@ -12,9 +12,9 @@ | ||
While developing [Babel](github.com/babel/babel) I developed a | ||
While developing [Babel](https://github.com/babel/babel) I followed a | ||
[monorepo](https://github.com/babel/babel/blob/master/doc/design/monorepo.md) approach | ||
where the entire project was split into individual packages but lived in the same repo. | ||
This was great. It allowed super easy modularisation which meant the core was easier to | ||
approach and meant others could use the useful parts of Babel in their applications. | ||
where the entire project was split into individual packages but everything lived in the same | ||
repo. This was great. It allowed super easy modularisation which meant the core was easier | ||
to approach and meant others could use the useful parts of Babel in their own projects. | ||
This tool was abstracted out of that and deals with bootstrapping these modules by linking | ||
This tool was abstracted out of that and deals with bootstrapping packages by linking | ||
them together as well as publishing them to npm. You can see the | ||
@@ -21,0 +21,0 @@ [Babel repo](https://github.com/babel/babel/tree/master/packages) for an example of a |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
16379
371