@microsoft/rush 5.65.1 → 5.66.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -4
- package/package.json +9 -9
package/README.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# @microsoft/rush
|
|
2
2
|
|
|
3
3
|
|
|
4
|
-
|
|
5
5
|
<br />
|
|
6
6
|
https://rushjs.io
|
|
7
7
|
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
|
|
26
26
|
- **Bulk publishing:** When it's time to do a release, Rush can detect which packages have changes, automatically bump all the appropriate version numbers, and run `npm publish` in each folder. If you like, configure your server to automatically run `rush publish` every hour.
|
|
27
27
|
|
|
28
|
-
- **Changelog tracking:** Whenever a PR is created, you can require developers to provide a major/minor/patch log entry for the affected projects. During publishing, these changes will be automatically aggregated into a nicely formatted [CHANGELOG.md](https://github.com/microsoft/rushstack/blob/
|
|
28
|
+
- **Changelog tracking:** Whenever a PR is created, you can require developers to provide a major/minor/patch log entry for the affected projects. During publishing, these changes will be automatically aggregated into a nicely formatted [CHANGELOG.md](https://github.com/microsoft/rushstack/blob/main/libraries/node-core-library/CHANGELOG.md) file.
|
|
29
29
|
|
|
30
30
|
- **Enterprise policies:** Want to review new libraries before developers add them to package.json, but avoid hassling people about already approved cases? Want to enforce that all your projects depend on the same library version numbers? Are unprofessional personal e-mail addresses accidentally showing up in your company's Git history? Rush can help maintain a consistent ecosystem when you've got many developers and many projects in the mix.
|
|
31
31
|
|
|
@@ -67,10 +67,10 @@ For more details and support resources, please visit: https://rushjs.io
|
|
|
67
67
|
## Links
|
|
68
68
|
|
|
69
69
|
- [CHANGELOG.md](
|
|
70
|
-
https://github.com/microsoft/rushstack/blob/
|
|
70
|
+
https://github.com/microsoft/rushstack/blob/main/apps/rush/CHANGELOG.md) - Find
|
|
71
71
|
out what's new in the latest version
|
|
72
72
|
- [UPGRADING.md](
|
|
73
|
-
https://github.com/microsoft/rushstack/blob/
|
|
73
|
+
https://github.com/microsoft/rushstack/blob/main/apps/rush/UPGRADING.md) - Instructions
|
|
74
74
|
for migrating existing projects to use a newer version of Rush
|
|
75
75
|
- [API Reference](https://api.rushstack.io/pages/rush-lib/)
|
|
76
76
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@microsoft/rush",
|
|
3
|
-
"version": "5.
|
|
3
|
+
"version": "5.66.2",
|
|
4
4
|
"description": "A professional solution for consolidating all your JavaScript projects in one Git repo",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"install",
|
|
@@ -29,17 +29,17 @@
|
|
|
29
29
|
},
|
|
30
30
|
"license": "MIT",
|
|
31
31
|
"dependencies": {
|
|
32
|
-
"@microsoft/rush-lib": "5.
|
|
33
|
-
"@rushstack/node-core-library": "3.45.
|
|
32
|
+
"@microsoft/rush-lib": "5.66.2",
|
|
33
|
+
"@rushstack/node-core-library": "3.45.2",
|
|
34
34
|
"colors": "~1.2.1",
|
|
35
35
|
"semver": "~7.3.0"
|
|
36
36
|
},
|
|
37
37
|
"devDependencies": {
|
|
38
|
-
"@rushstack/eslint-config": "2.5.
|
|
39
|
-
"@rushstack/heft": "0.44.
|
|
40
|
-
"@rushstack/heft-node-rig": "1.8.
|
|
41
|
-
"@rushstack/rush-amazon-s3-build-cache-plugin": "5.
|
|
42
|
-
"@rushstack/rush-azure-storage-build-cache-plugin": "5.
|
|
38
|
+
"@rushstack/eslint-config": "2.5.3",
|
|
39
|
+
"@rushstack/heft": "0.44.10",
|
|
40
|
+
"@rushstack/heft-node-rig": "1.8.8",
|
|
41
|
+
"@rushstack/rush-amazon-s3-build-cache-plugin": "5.66.2",
|
|
42
|
+
"@rushstack/rush-azure-storage-build-cache-plugin": "5.66.2",
|
|
43
43
|
"@types/heft-jest": "1.0.1",
|
|
44
44
|
"@types/node": "12.20.24",
|
|
45
45
|
"@types/semver": "7.3.5"
|
|
@@ -50,5 +50,5 @@
|
|
|
50
50
|
"_phase:build": "heft build --clean",
|
|
51
51
|
"_phase:test": "heft test --no-build"
|
|
52
52
|
},
|
|
53
|
-
"readme": "# @microsoft/rush\n\n\n![rush](https://github.com/microsoft/rushstack/blob/
|
|
53
|
+
"readme": "# @microsoft/rush\n\n\n\n<br />\n https://rushjs.io\n\n<!-- ------------------------------------------------------------------ -->\n<!-- Text below this line should stay in sync with the web site content -->\n<!-- ------------------------------------------------------------------ -->\n\n**Rush** makes life easier for JavaScript developers who build and publish many NPM packages at once. If you're looking to consolidate all your projects into a single repo, you came to the right place! Rush is a fast, professional solution for managing this scenario. It gives you:\n\n- **A single NPM install:** In one step, Rush installs all the dependencies for all your projects into a common folder. This is not just a \"package.json\" file at the root of your repo (which might set you up to accidentally `require()` a sibling's dependencies). Instead, Rush uses symlinks to reconstruct an accurate \"node_modules\" folder for each project, without any of the limitations or glitches that seem to plague other approaches.\n\n ⏵ **This algorithm supports the [PNPM, NPM, and Yarn](https://rushjs.io/pages/maintainer/package_managers/) package managers.**\n\n- **Automatic local linking:** Inside a Rush repo, all your projects are automatically symlinked to each other. When you make a change, you can see the downstream effects without publishing anything, and without any `npm link` headaches. If you don't want certain projects to get linked, that's supported, too.\n\n- **Fast builds:** Rush detects your dependency graph and builds your projects in the right order. If two packages don't directly depend on each other, Rush parallelizes their build as separate Node.js processes (and shows live console output in a [readable order](https://www.npmjs.com/package/@rushstack/stream-collator)). In practice this multi-process approach can yield more significant speedups than all those async functions in your single-threaded Gulpfile.\n\n- **Subset and incremental builds:** If you only plan to work with a few projects from your repo, `rush rebuild --to <project>` does a clean build of just your upstream dependencies. After you make changes, `rush rebuild --from <project>` does a clean build of only the affected downstream projects. And if your toolchain is [package-deps-hash](https://www.npmjs.com/package/@rushstack/package-deps-hash) enabled, `rush build` delivers a powerful cross-project incremental build (that also supports subset builds).\n\n- **Cyclic dependencies:** If you have hammers that build hammer-factory-factories, Rush has you covered! When a package indirectly depends on an older version of itself, projects in the cycle use the last published version, whereas other projects still get the latest bits.\n\n- **Bulk publishing:** When it's time to do a release, Rush can detect which packages have changes, automatically bump all the appropriate version numbers, and run `npm publish` in each folder. If you like, configure your server to automatically run `rush publish` every hour.\n\n- **Changelog tracking:** Whenever a PR is created, you can require developers to provide a major/minor/patch log entry for the affected projects. During publishing, these changes will be automatically aggregated into a nicely formatted [CHANGELOG.md](https://github.com/microsoft/rushstack/blob/main/libraries/node-core-library/CHANGELOG.md) file.\n\n- **Enterprise policies:** Want to review new libraries before developers add them to package.json, but avoid hassling people about already approved cases? Want to enforce that all your projects depend on the same library version numbers? Are unprofessional personal e-mail addresses accidentally showing up in your company's Git history? Rush can help maintain a consistent ecosystem when you've got many developers and many projects in the mix.\n\n- **Lots more!** Rush was created by the platform team for [Microsoft SharePoint](http://aka.ms/spfx). We build hundreds of production NPM packages every day, from internal and public Git repositories, for third party SDKs and live services with millions of users. If there's an important package management problem that needs solvin', it's likely to end up as a feature for Rush.\n\n\n# 3 Minute Demo\n\nSee Rush in action! From your shell, install the tool like this:\n```\n$ npm install -g @microsoft/rush\n```\n\nFor command-line help, do this:\n```\n$ rush -h\n```\n\nTo see Rush build some real projects, try running these commands: :-)\n```\n$ git clone https://github.com/microsoft/rushstack\n$ cd rushstack\n$ rush install\n$ rush install # <-- instantaneous!\n$ rush rebuild\n$ rush build # <-- instantaneous!\n```\n_(If you don't have a GitHub account set up, you can use `rush install --bypass-policy`.)_\n\n\n<!-- ------------------------------------------------------------------ -->\n<!-- Text above this line should stay in sync with the web site content -->\n<!-- ------------------------------------------------------------------ -->\n\n## Getting Started\n\nFor more details and support resources, please visit: https://rushjs.io\n\n## Links\n\n- [CHANGELOG.md](\n https://github.com/microsoft/rushstack/blob/main/apps/rush/CHANGELOG.md) - Find\n out what's new in the latest version\n- [UPGRADING.md](\n https://github.com/microsoft/rushstack/blob/main/apps/rush/UPGRADING.md) - Instructions\n for migrating existing projects to use a newer version of Rush\n- [API Reference](https://api.rushstack.io/pages/rush-lib/)\n\nRush is part of the [Rush Stack](https://rushstack.io/) family of projects.\n"
|
|
54
54
|
}
|