Skip to content

Commit 4078071

Browse files
ShMcKShMcK
committed
update v0.3.0 patch
1 parent c1d63d1 commit 4078071

File tree

2 files changed

+42
-42
lines changed

2 files changed

+42
-42
lines changed

‎CODEROAD.md

+21-21
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ config:
1010
actions:
1111
commits:
1212
- '55a9b6d'
13-
- '34f028e'
13+
- 'd58d630'
1414
commands:
1515
- npm install
1616
repo:
@@ -54,14 +54,14 @@ setup:
5454
files:
5555
- package.json
5656
commits:
57-
- 'c3b4350'
57+
- '5326ec8'
5858
commands:
5959
- npm install
6060
solution:
6161
files:
6262
- package.json
6363
commits:
64-
- '02cd4f2'
64+
- '424cf66'
6565
```
6666

6767
Add your name as the `author` of the project in the package.json file.
@@ -89,12 +89,12 @@ setup:
8989
files:
9090
- package.json
9191
commits:
92-
- '1917199'
92+
- '68ddb97'
9393
solution:
9494
files:
9595
- package.json
9696
commits:
97-
- 'e8b3d85'
97+
- '138ad0e'
9898
```
9999

100100
Add a `description` to the package.json file of your project.
@@ -122,12 +122,12 @@ setup:
122122
files:
123123
- package.json
124124
commits:
125-
- '2ba75f8'
125+
- '2069439'
126126
solution:
127127
files:
128128
- package.json
129129
commits:
130-
- '63cd193'
130+
- 'f2ed460'
131131
```
132132

133133
Add an array of suitable strings to the `keywords` field in the package.json file of your project.
@@ -153,12 +153,12 @@ setup:
153153
files:
154154
- package.json
155155
commits:
156-
- 'acd63ba'
156+
- 'f2229d1'
157157
solution:
158158
files:
159159
- package.json
160160
commits:
161-
- 'a64411c'
161+
- '9378267'
162162
```
163163

164164
Fill the `license` field in the package.json file of your project as you find suitable.
@@ -180,12 +180,12 @@ setup:
180180
files:
181181
- package.json
182182
commits:
183-
- '580d786'
183+
- '60a4e7b'
184184
solution:
185185
files:
186186
- package.json
187187
commits:
188-
- 'a92903d'
188+
- 'f9f7f29'
189189
```
190190

191191
Add a `version` to the package.json file of your project.
@@ -222,15 +222,15 @@ setup:
222222
files:
223223
- package.json
224224
commits:
225-
- 'eafc39a'
225+
- 'e97c095'
226226
watchers:
227227
- package.json
228228
- node_modules/moment
229229
solution:
230230
files:
231231
- package.json
232232
commits:
233-
- '50da157'
233+
- '97af83a'
234234
```
235235

236236
Install the "moment" package to the `dependencies` field of your package.json file by running the command line npm install.
@@ -269,15 +269,15 @@ setup:
269269
files:
270270
- package.json
271271
commits:
272-
- 'e658c66'
272+
- 'be03933'
273273
watchers:
274274
- package.json
275275
- node_modules/moment
276276
solution:
277277
files:
278278
- package.json
279279
commits:
280-
- 'f10433e'
280+
- 'ba77ae7'
281281
```
282282

283283
In the dependencies section of your package.json file, change the `version` of moment to match MAJOR version 2, MINOR version 10 and PATCH version 2
@@ -301,12 +301,12 @@ setup:
301301
files:
302302
- package.json
303303
commits:
304-
- 'b4edb0c'
304+
- 'c4ff0f6'
305305
solution:
306306
files:
307307
- package.json
308308
commits:
309-
- '8e169e1'
309+
- 'cc1f2a5'
310310
```
311311

312312
In the package.json file, your current rule for how npm may upgrade moment is to use a specific version (2.10.2). But now, you want to allow the latest 2.10.x version.
@@ -335,12 +335,12 @@ setup:
335335
files:
336336
- package.json
337337
commits:
338-
- '67c5f7b'
338+
- 'fb75ecf'
339339
solution:
340340
files:
341341
- package.json
342342
commits:
343-
- '601c5fe'
343+
- 'd0e1a22'
344344
```
345345

346346
Use the caret (`^`) to prefix the version of moment in your dependencies and allow npm to update it to any new MINOR release.
@@ -364,12 +364,12 @@ setup:
364364
files:
365365
- package.json
366366
commits:
367-
- '4359bde'
367+
- 'da1e99e'
368368
solution:
369369
files:
370370
- package.json
371371
commits:
372-
- 'f8cfb51'
372+
- '796b176'
373373
```
374374

375375
Remove the moment package from your dependencies.

‎coderoad-config.json

+21-21
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
"command": "npm run programmatic-test",
1010
"path": "coderoad",
1111
"actions": {
12-
"commits": ["55a9b6d", "34f028e"],
12+
"commits": ["55a9b6d", "d58d630"],
1313
"commands": ["npm install"]
1414
}
1515
},
@@ -42,12 +42,12 @@
4242
"id": "L2:S1",
4343
"setup": {
4444
"files": ["package.json"],
45-
"commits": ["c3b4350"],
45+
"commits": ["5326ec8"],
4646
"commands": ["npm install"]
4747
},
4848
"solution": {
4949
"files": ["package.json"],
50-
"commits": ["02cd4f2"]
50+
"commits": ["424cf66"]
5151
},
5252
"content": "Add your name as the `author` of the project in the package.json file.\n**Note:** Remember that you’re writing JSON, so all field names must use double-quotes (\") and be separated with a comma (,).\n\n"
5353
}
@@ -64,11 +64,11 @@
6464
"id": "L3:S1",
6565
"setup": {
6666
"files": ["package.json"],
67-
"commits": ["1917199"]
67+
"commits": ["68ddb97"]
6868
},
6969
"solution": {
7070
"files": ["package.json"],
71-
"commits": ["e8b3d85"]
71+
"commits": ["138ad0e"]
7272
},
7373
"content": "Add a `description` to the package.json file of your project.\n\n**Note:** Remember to use double-quotes for field-names (\") and commas (,) to separate fields.\n\n"
7474
}
@@ -85,11 +85,11 @@
8585
"id": "L4:S1",
8686
"setup": {
8787
"files": ["package.json"],
88-
"commits": ["2ba75f8"]
88+
"commits": ["2069439"]
8989
},
9090
"solution": {
9191
"files": ["package.json"],
92-
"commits": ["63cd193"]
92+
"commits": ["f2ed460"]
9393
},
9494
"content": "Add an array of suitable strings to the `keywords` field in the package.json file of your project.\n\nOne of the keywords should be \"freecodecamp\".\n"
9595
}
@@ -106,11 +106,11 @@
106106
"id": "L5:S1",
107107
"setup": {
108108
"files": ["package.json"],
109-
"commits": ["acd63ba"]
109+
"commits": ["f2229d1"]
110110
},
111111
"solution": {
112112
"files": ["package.json"],
113-
"commits": ["a64411c"]
113+
"commits": ["9378267"]
114114
},
115115
"content": "Fill the `license` field in the package.json file of your project as you find suitable.\n\n"
116116
}
@@ -127,11 +127,11 @@
127127
"id": "L6:S1",
128128
"setup": {
129129
"files": ["package.json"],
130-
"commits": ["580d786"]
130+
"commits": ["60a4e7b"]
131131
},
132132
"solution": {
133133
"files": ["package.json"],
134-
"commits": ["a92903d"]
134+
"commits": ["f9f7f29"]
135135
},
136136
"content": "Add a `version` to the package.json file of your project.\n\n"
137137
}
@@ -148,12 +148,12 @@
148148
"id": "L7:S1",
149149
"setup": {
150150
"files": ["package.json"],
151-
"commits": ["eafc39a"],
151+
"commits": ["e97c095"],
152152
"watchers": ["package.json", "node_modules/moment"]
153153
},
154154
"solution": {
155155
"files": ["package.json"],
156-
"commits": ["50da157"]
156+
"commits": ["97af83a"]
157157
},
158158
"content": "Install the \"moment\" package to the `dependencies` field of your package.json file by running the command line npm install.\n\n**Note:** Moment is a handy library for working with time and dates.\n\n"
159159
}
@@ -170,12 +170,12 @@
170170
"id": "L8:S1",
171171
"setup": {
172172
"files": ["package.json"],
173-
"commits": ["e658c66"],
173+
"commits": ["be03933"],
174174
"watchers": ["package.json", "node_modules/moment"]
175175
},
176176
"solution": {
177177
"files": ["package.json"],
178-
"commits": ["f10433e"]
178+
"commits": ["ba77ae7"]
179179
},
180180
"content": "In the dependencies section of your package.json file, change the `version` of moment to match MAJOR version 2, MINOR version 10 and PATCH version 2\n\n"
181181
}
@@ -192,11 +192,11 @@
192192
"id": "L9:S1",
193193
"setup": {
194194
"files": ["package.json"],
195-
"commits": ["b4edb0c"]
195+
"commits": ["c4ff0f6"]
196196
},
197197
"solution": {
198198
"files": ["package.json"],
199-
"commits": ["8e169e1"]
199+
"commits": ["cc1f2a5"]
200200
},
201201
"content": "In the package.json file, your current rule for how npm may upgrade moment is to use a specific version (2.10.2). But now, you want to allow the latest 2.10.x version.\nUse the tilde (`~`) character to prefix the version of moment in your dependencies, and allow npm to update it to any new PATCH release.\n\n**Note:** The version numbers themselves should not be changed.\n\n"
202202
}
@@ -213,11 +213,11 @@
213213
"id": "L10:S1",
214214
"setup": {
215215
"files": ["package.json"],
216-
"commits": ["67c5f7b"]
216+
"commits": ["fb75ecf"]
217217
},
218218
"solution": {
219219
"files": ["package.json"],
220-
"commits": ["601c5fe"]
220+
"commits": ["d0e1a22"]
221221
},
222222
"content": "Use the caret (`^`) to prefix the version of moment in your dependencies and allow npm to update it to any new MINOR release.\n\n**Note:** The version numbers themselves should not be changed.\n\n"
223223
}
@@ -234,11 +234,11 @@
234234
"id": "L11:S1`",
235235
"setup": {
236236
"files": ["package.json"],
237-
"commits": ["4359bde"]
237+
"commits": ["da1e99e"]
238238
},
239239
"solution": {
240240
"files": ["package.json"],
241-
"commits": ["f8cfb51"]
241+
"commits": ["796b176"]
242242
},
243243
"content": "Remove the moment package from your dependencies.\n\n**Note:** Make sure you have the right amount of commas after removing it.\n\n"
244244
}

0 commit comments

Comments
 (0)