Skip to content

Commit 43145c5

Browse files
author
Nick Pape
committed
Rush init --overwrite
1 parent 3e652e8 commit 43145c5

File tree

9 files changed

+651
-118
lines changed

9 files changed

+651
-118
lines changed

‎.gitattributes‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,7 @@
6363
/*/*/bin/+([!.]) -text
6464

6565
# Don't allow people to merge changes to these generated files, because the result
66-
# may be invalid. You need to run "rush generate" again.
66+
# may be invalid. You need to run "rush update" again.
6767
shrinkwrap.yaml merge=binary
6868
npm-shrinkwrap.json merge=binary
69+
yarn.lock merge=binary

‎.gitignore‎

Lines changed: 59 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -1,68 +1,65 @@
1-
# Windows OS Files
2-
$RECYCLE.BIN/
3-
Desktop.ini
4-
Thumbs.db
5-
ehthumbs.db
6-
7-
# Mac OSX Files
8-
.AppleDouble
9-
.DS_Store
10-
.LSOverride
11-
.Spotlight-V100
12-
.Trashes
13-
._*
14-
15-
# Package files
16-
app
17-
app-min
18-
bower_components
1+
# Logs
2+
*.log
3+
npm-debug.log*
4+
yarn-debug.log*
5+
yarn-error.log*
6+
7+
# Runtime data
8+
*.pid
9+
*.seed
10+
*.pid.lock
11+
12+
# Directory for instrumented libs generated by jscoverage/JSCover
13+
lib-cov
14+
15+
# Coverage directory used by tools like istanbul
1916
coverage
20-
local
21-
dist
22-
jspm_packages
17+
18+
# nyc test coverage
19+
.nyc_output
20+
21+
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
22+
.grunt
23+
24+
# Bower dependency directory (https://bower.io/)
25+
bower_components
26+
27+
# node-waf configuration
28+
.lock-wscript
29+
30+
# Compiled binary addons (https://nodejs.org/api/addons.html)
31+
build/Release
32+
33+
# Dependency directories
34+
node_modules/
35+
jspm_packages/
36+
37+
# Optional npm cache directory
38+
.npm
39+
40+
# Optional eslint cache
41+
.eslintcache
42+
43+
# Optional REPL history
44+
.node_repl_history
45+
46+
# Output of 'npm pack'
47+
*.tgz
48+
49+
# Yarn Integrity file
50+
.yarn-integrity
51+
52+
# dotenv environment variables file
53+
.env
54+
55+
# next.js build output
56+
.next
57+
58+
# Common toolchain intermediate files
2359
lib
24-
lib-amd
25-
lib-es6
26-
node_modules
27-
npm-debug.log
28-
pnpm-debug.log
29-
npminstall-log.txt
60+
dist
3061
temp
3162

3263
# Rush files
33-
**/*.build.error.log
34-
**/*.build.log
35-
/common/apiDocs/json/**
36-
/common/last-install.flag
37-
/common/last-install.log
38-
/common/local-npm
39-
/common/local-npm/**
40-
/common/local-rush
41-
/common/local-rush/**
42-
/common/npm-cache
43-
/common/npm-cache/**
44-
/common/npm-local
45-
/common/npm-local/**
46-
/common/npm-tmp
47-
/common/npm-tmp/**
48-
/common/rush-link.json
49-
/common/rush-recycler
64+
common/temp/**
5065
package-deps.json
51-
52-
# IDE files
53-
*.bak
54-
*.csproj.user
55-
*.sublime-project
56-
*.sublime-workspace
57-
*.suo
58-
*.userosscache
59-
.idea
60-
.vs/
61-
/.settings/
62-
bin/
63-
64-
# Ignore VS Code personal settings, but keep a root-level setting
65-
/*/**/.vscode/
66-
67-
# Build artifacts
68-
**/*.scss.ts

‎.travis.yml‎

Lines changed: 22 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,22 @@
1-
language: node_js
2-
node_js:
3-
- '8.9.4'
4-
script:
5-
- set -e
6-
- echo 'Checking change file...' && echo -en 'travis_fold:start:change\\r'
7-
- git fetch origin master:refs/remotes/origin/master -a
8-
- node common/scripts/install-run-rush.js change -v
9-
- echo -en 'travis_fold:end:change\\r'
10-
- echo 'Running rush check' && echo -en 'travis_fold:start:check\\r'
11-
- node common/scripts/install-run-rush.js check
12-
- echo -en 'travis_fold:end:check\\r'
13-
- echo 'Installing...' && echo -en 'travis_fold:start:install\\r'
14-
- node common/scripts/install-run-rush.js install --bypass-policy
15-
- echo -en 'travis_fold:end:install\\r'
16-
- echo 'Building...' && echo -en 'travis_fold:start:build\\r'
17-
- node common/scripts/install-run-rush.js rebuild --verbose --production
18-
- echo -en 'travis_fold:end:build\\r'
1+
language: node_js
2+
node_js:
3+
- '8.9.4'
4+
script:
5+
- set -e
6+
7+
- echo 'Checking for missing change logs...' && echo -en 'travis_fold:start:change\\r'
8+
- git fetch origin master:refs/remotes/origin/master -a
9+
- node common/scripts/install-run-rush.js change -v
10+
- echo -en 'travis_fold:end:change\\r'
11+
12+
- echo 'Checking for inconsistent dependency versions' && echo -en 'travis_fold:start:check\\r'
13+
- node common/scripts/install-run-rush.js check
14+
- echo -en 'travis_fold:end:check\\r'
15+
16+
- echo 'Installing...' && echo -en 'travis_fold:start:install\\r'
17+
- node common/scripts/install-run-rush.js install
18+
- echo -en 'travis_fold:end:install\\r'
19+
20+
- echo 'Building...' && echo -en 'travis_fold:start:build\\r'
21+
- node common/scripts/install-run-rush.js rebuild --verbose --production
22+
- echo -en 'travis_fold:end:build\\r'

‎common/config/rush/.npmrc‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,12 @@
1+
# Rush uses this file to configure the package registry, regardless of whether the
2+
# package manager is PNPM, NPM, or Yarn. Prior to invoking the package manager,
3+
# Rush will always copy this file to the folder where installation is performed.
4+
# When NPM is the package manager, Rush works around NPM's processing of
5+
# undefined environment variables by deleting any lines that reference undefined
6+
# environment variables.
7+
#
8+
# DO NOT SPECIFY AUTHENTICATION CREDENTIALS IN THIS FILE. It should only be used
9+
# to configure registry sources.
10+
111
registry=https://registry.npmjs.org/
212
always-auth=false

‎common/config/rush/command-line.json‎

Lines changed: 172 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,178 @@
1+
/**
2+
* This configuration file defines custom commands for the "rush" command-line.
3+
* For full documentation, please see https://rushjs.io
4+
*/
15
{
26
"$schema": "https://developer.microsoft.com/json-schemas/rush/v5/command-line.schema.json",
37

8+
/**
9+
* Custom "commands" introduce new verbs for the command-line. To see the help for these
10+
* example commands, try "rush --help", "rush my-bulk-command --help", or
11+
* "rush my-global-command --help".
12+
*/
13+
"commands": [
14+
// {
15+
// /**
16+
// * (Required) Determines the type of custom command.
17+
// * Rush's "bulk" commands are invoked separately for each project. Rush will look in
18+
// * each project's package.json file for a "scripts" entry whose name matches the
19+
// * command name. By default, the command will run for every project in the repo,
20+
// * according to the dependency graph (similar to how "rush build" works).
21+
// * The set of projects can be restricted e.g. using the "--to" or "--from" parameters.
22+
// */
23+
// "commandKind": "bulk",
24+
//
25+
// /**
26+
// * (Required) The name that will be typed as part of the command line. This is also the name
27+
// * of the "scripts" hook in the project's package.json file.
28+
// * The name should be comprised of lower case words separated by hyphens.
29+
// */
30+
// "name": "my-bulk-command",
31+
//
32+
// /**
33+
// * (Required) A short summary of the custom command to be shown when printing command line
34+
// * help, e.g. "rush --help".
35+
// */
36+
// "summary": "Example bulk custom command",
37+
//
38+
// /**
39+
// * A detailed description of the command to be shown when printing command line
40+
// * help (e.g. "rush --help my-command").
41+
// * If omitted, the "summary" text will be shown instead.
42+
// *
43+
// * Whenever you introduce commands/parameters, taking a little time to write meaningful
44+
// * documentation can make a big difference for the developer experience in your repo.
45+
// */
46+
// "description": "This is an example custom command that runs separately for each project",
47+
//
48+
// /**
49+
// * (Required) If true, then this command is safe to be run in parallel, i.e. executed
50+
// * simultaneously for multiple projects. Similar to "rush build", regardless of parallelism
51+
// * projects will not start processing until their dependencies have completed processing.
52+
// */
53+
// "enableParallelism": false,
54+
//
55+
// /**
56+
// * Normally Rush requires that each project's package.json has a "scripts" entry matching
57+
// * the custom command name. To disable this check, set "ignoreMissingScript" to true;
58+
// * projects with a missing definition will be skipped.
59+
// */
60+
// "ignoreMissingScript": false
61+
// },
62+
//
63+
// {
64+
// /**
65+
// * (Required) Determines the type of custom command.
66+
// * Rush's "global" commands are invoked once for the entire repo.
67+
// */
68+
// "commandKind": "global",
69+
//
70+
// "name": "my-global-command",
71+
// "summary": "Example global custom command",
72+
// "description": "This is an example custom command that runs once for the entire repo",
73+
//
74+
// /**
75+
// * A script that will be invoked using the OS shell. The working directory will be the folder
76+
// * that contains rush.json. If custom parameters are associated with this command, their
77+
// * values will be appended to the end of this string.
78+
// */
79+
// "shellCommand": "node common/scripts/my-global-command.js"
80+
// }
81+
],
82+
83+
/**
84+
* Custom "parameters" introduce new parameters for specified Rush command-line commands.
85+
* For example, you might define a "--production" parameter for the "rush build" command.
86+
*/
487
"parameters": [
88+
// {
89+
// /**
90+
// * (Required) Determines the type of custom parameter.
91+
// * A "flag" is a custom command-line parameter whose presence acts as an on/off switch.
92+
// */
93+
// "parameterKind": "flag",
94+
//
95+
// /**
96+
// * (Required) The long name of the parameter. It must be lower-case and use dash delimiters.
97+
// */
98+
// "longName": "--my-flag",
99+
//
100+
// /**
101+
// * An optional alternative short name for the parameter. It must be a dash followed by a single
102+
// * lower-case or upper-case letter, which is case-sensitive.
103+
// *
104+
// * NOTE: The Rush developers recommend that automation scripts should always use the long name
105+
// * to improve readability. The short name is only intended as a convenience for humans.
106+
// * The alphabet letters run out quickly, and are difficult to memorize, so *only* use
107+
// * a short name if you expect the parameter to be needed very often in everyday operations.
108+
// */
109+
// "shortName": "-m",
110+
//
111+
// /**
112+
// * (Required) A long description to be shown in the command-line help.
113+
// *
114+
// * Whenever you introduce commands/parameters, taking a little time to write meaningful
115+
// * documentation can make a big difference for the developer experience in your repo.
116+
// */
117+
// "description": "A custom flag parameter that is passed to the scripts that are invoked when building projects",
118+
//
119+
// /**
120+
// * (Required) A list of custom commands and/or built-in Rush commands that this parameter may
121+
// * be used with. The parameter will be appended to the shell command that Rush invokes.
122+
// */
123+
// "associatedCommands": [ "build", "rebuild" ]
124+
// },
125+
//
126+
// {
127+
// /**
128+
// * (Required) Determines the type of custom parameter.
129+
// * A "flag" is a custom command-line parameter whose presence acts as an on/off switch.
130+
// */
131+
// "parameterKind": "choice",
132+
// "longName": "--my-choice",
133+
// "description": "A custom choice parameter for the \"my-global-command\" custom command",
134+
//
135+
// "associatedCommands": [ "my-global-command" ],
136+
//
137+
// /**
138+
// * Normally if a parameter is omitted from the command line, it will not be passed
139+
// * to the shell command. this value will be inserted by default. Whereas if a "defaultValue"
140+
// * is defined, the parameter will always be passed to the shell command, and will use the
141+
// * default value if unspecified. The value must be one of the defined alternatives.
142+
// */
143+
// "defaultValue": "vanilla",
144+
//
145+
// /**
146+
// * (Required) A list of alternative argument values that can be chosen for this parameter.
147+
// */
148+
// "alternatives": [
149+
// {
150+
// /**
151+
// * A token that is one of the alternatives that can be used with the choice parameter,
152+
// * e.g. "vanilla" in "--flavor vanilla".
153+
// */
154+
// "name": "vanilla",
155+
//
156+
// /**
157+
// * A detailed description for the alternative that can be shown in the command-line help.
158+
// *
159+
// * Whenever you introduce commands/parameters, taking a little time to write meaningful
160+
// * documentation can make a big difference for the developer experience in your repo.
161+
// */
162+
// "description": "Use the vanilla flavor (the default)"
163+
// },
164+
//
165+
// {
166+
// "name": "chocolate",
167+
// "description": "Use the chocolate flavor"
168+
// },
169+
//
170+
// {
171+
// "name": "strawberry",
172+
// "description": "Use the strawberry flavor"
173+
// }
174+
// ]
175+
// }
5176
{
6177
"longName": "--no-color",
7178
"parameterKind": "flag",
@@ -15,4 +186,4 @@
15186
"associatedCommands": [ "build", "rebuild" ]
16187
}
17188
]
18-
}
189+
}

0 commit comments

Comments
 (0)