aymericbeaumet/metalsmith-concat

:paperclip: Metalsmith plugin to concatenate files

👋 My name's Aymeric, I'm a Software Engineer living in Paris, France.

🔭 I have a keen interest in Rust. I also like Go.

✍️ I sometime write on my blog.

📫 You can reach out to me by mail or on Twitter.

metalsmith-concat's Issues

v6.0.3 [email protected] postinstall Fails

I'm having this issue with a project of mine, but I get the error even with a new directory:

$ mkdir concat && cd concat && npm install --save metalsmith-concat

> [email protected] postinstall /Users/christianemmer/concat/node_modules/metalsmith-concat
> cd example && npm install

sh: line 0: cd: example: No such file or directory
npm WARN enoent ENOENT: no such file or directory, open '/Users/christianemmer/concat/package.json'
npm WARN concat No description
npm WARN concat No repository field.
npm WARN concat No README data
npm WARN concat No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `cd example && npm install`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/christianemmer/.npm/_logs/2019-03-21T18_56_43_875Z-debug.log

Here's the debug log:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   '--save',
1 verbose cli   'metalsmith-concat' ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session ae8496ea2325c999
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 200 https://registry.npmjs.org/metalsmith-concat 14ms (from cache)
8 silly pacote tag manifest for metalsmith-concat@latest fetched in 24ms
9 timing stage:loadCurrentTree Completed in 54ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 1ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 0ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule [email protected] checking installable status
17 http fetch GET 200 https://registry.npmjs.org/async 18ms (from cache)
18 http fetch GET 200 https://registry.npmjs.org/minimatch 17ms (from cache)
19 http fetch GET 200 https://registry.npmjs.org/glob 19ms (from cache)
20 silly pacote version manifest for [email protected] fetched in 23ms
21 silly resolveWithNewModule [email protected] checking installable status
22 silly pacote version manifest for [email protected] fetched in 22ms
23 silly resolveWithNewModule [email protected] checking installable status
24 silly pacote version manifest for [email protected] fetched in 23ms
25 silly resolveWithNewModule [email protected] checking installable status
26 http fetch GET 304 https://registry.npmjs.org/lodash 133ms (from cache)
27 silly pacote range manifest for lodash@^4.17.11 fetched in 135ms
28 silly resolveWithNewModule [email protected] checking installable status
29 http fetch GET 200 https://registry.npmjs.org/fs.realpath 17ms (from cache)
30 http fetch GET 200 https://registry.npmjs.org/inherits 15ms (from cache)
31 http fetch GET 200 https://registry.npmjs.org/inflight 17ms (from cache)
32 http fetch GET 200 https://registry.npmjs.org/path-is-absolute 16ms (from cache)
33 silly pacote range manifest for fs.realpath@^1.0.0 fetched in 20ms
34 silly resolveWithNewModule [email protected] checking installable status
35 silly pacote range manifest for inherits@2 fetched in 19ms
36 silly resolveWithNewModule [email protected] checking installable status
37 silly pacote range manifest for inflight@^1.0.4 fetched in 23ms
38 silly resolveWithNewModule [email protected] checking installable status
39 silly pacote range manifest for path-is-absolute@^1.0.0 fetched in 37ms
40 silly resolveWithNewModule [email protected] checking installable status
41 http fetch GET 304 https://registry.npmjs.org/once 47ms (from cache)
42 silly pacote range manifest for once@^1.3.0 fetched in 49ms
43 silly resolveWithNewModule [email protected] checking installable status
44 http fetch GET 304 https://registry.npmjs.org/wrappy 30ms (from cache)
45 silly pacote range manifest for wrappy@1 fetched in 31ms
46 silly resolveWithNewModule [email protected] checking installable status
47 http fetch GET 200 https://registry.npmjs.org/brace-expansion 4ms (from cache)
48 silly pacote range manifest for brace-expansion@^1.1.7 fetched in 5ms
49 silly resolveWithNewModule [email protected] checking installable status
50 http fetch GET 200 https://registry.npmjs.org/balanced-match 7ms (from cache)
51 http fetch GET 200 https://registry.npmjs.org/concat-map 8ms (from cache)
52 silly pacote range manifest for balanced-match@^1.0.0 fetched in 9ms
53 silly resolveWithNewModule [email protected] checking installable status
54 silly pacote version manifest for [email protected] fetched in 9ms
55 silly resolveWithNewModule [email protected] checking installable status
56 timing stage:loadIdealTree:loadAllDepsIntoIdealTree Completed in 272ms
57 timing stage:loadIdealTree Completed in 279ms
58 silly currentTree concat
59 silly idealTree concat
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree ├── [email protected]
59 silly idealTree └── [email protected]
60 silly install generateActionsToTake
61 timing stage:generateActionsToTake Completed in 5ms
62 silly diffTrees action count 14
63 silly diffTrees add [email protected]
64 silly diffTrees add [email protected]
65 silly diffTrees add [email protected]
66 silly diffTrees add [email protected]
67 silly diffTrees add [email protected]
68 silly diffTrees add [email protected]
69 silly diffTrees add [email protected]
70 silly diffTrees add [email protected]
71 silly diffTrees add [email protected]
72 silly diffTrees add [email protected]
73 silly diffTrees add [email protected]
74 silly diffTrees add [email protected]
75 silly diffTrees add [email protected]
76 silly diffTrees add [email protected]
77 silly decomposeActions action count 112
78 silly decomposeActions fetch [email protected]
79 silly decomposeActions extract [email protected]
80 silly decomposeActions preinstall [email protected]
81 silly decomposeActions build [email protected]
82 silly decomposeActions install [email protected]
83 silly decomposeActions postinstall [email protected]
84 silly decomposeActions finalize [email protected]
85 silly decomposeActions refresh-package-json [email protected]
86 silly decomposeActions fetch [email protected]
87 silly decomposeActions extract [email protected]
88 silly decomposeActions preinstall [email protected]
89 silly decomposeActions build [email protected]
90 silly decomposeActions install [email protected]
91 silly decomposeActions postinstall [email protected]
92 silly decomposeActions finalize [email protected]
93 silly decomposeActions refresh-package-json [email protected]
94 silly decomposeActions fetch [email protected]
95 silly decomposeActions extract [email protected]
96 silly decomposeActions preinstall [email protected]
97 silly decomposeActions build [email protected]
98 silly decomposeActions install [email protected]
99 silly decomposeActions postinstall [email protected]
100 silly decomposeActions finalize [email protected]
101 silly decomposeActions refresh-package-json [email protected]
102 silly decomposeActions fetch [email protected]
103 silly decomposeActions extract [email protected]
104 silly decomposeActions preinstall [email protected]
105 silly decomposeActions build [email protected]
106 silly decomposeActions install [email protected]
107 silly decomposeActions postinstall [email protected]
108 silly decomposeActions finalize [email protected]
109 silly decomposeActions refresh-package-json [email protected]
110 silly decomposeActions fetch [email protected]
111 silly decomposeActions extract [email protected]
112 silly decomposeActions preinstall [email protected]
113 silly decomposeActions build [email protected]
114 silly decomposeActions install [email protected]
115 silly decomposeActions postinstall [email protected]
116 silly decomposeActions finalize [email protected]
117 silly decomposeActions refresh-package-json [email protected]
118 silly decomposeActions fetch [email protected]
119 silly decomposeActions extract [email protected]
120 silly decomposeActions preinstall [email protected]
121 silly decomposeActions build [email protected]
122 silly decomposeActions install [email protected]
123 silly decomposeActions postinstall [email protected]
124 silly decomposeActions finalize [email protected]
125 silly decomposeActions refresh-package-json [email protected]
126 silly decomposeActions fetch [email protected]
127 silly decomposeActions extract [email protected]
128 silly decomposeActions preinstall [email protected]
129 silly decomposeActions build [email protected]
130 silly decomposeActions install [email protected]
131 silly decomposeActions postinstall [email protected]
132 silly decomposeActions finalize [email protected]
133 silly decomposeActions refresh-package-json [email protected]
134 silly decomposeActions fetch [email protected]
135 silly decomposeActions extract [email protected]
136 silly decomposeActions preinstall [email protected]
137 silly decomposeActions build [email protected]
138 silly decomposeActions install [email protected]
139 silly decomposeActions postinstall [email protected]
140 silly decomposeActions finalize [email protected]
141 silly decomposeActions refresh-package-json [email protected]
142 silly decomposeActions fetch [email protected]
143 silly decomposeActions extract [email protected]
144 silly decomposeActions preinstall [email protected]
145 silly decomposeActions build [email protected]
146 silly decomposeActions install [email protected]
147 silly decomposeActions postinstall [email protected]
148 silly decomposeActions finalize [email protected]
149 silly decomposeActions refresh-package-json [email protected]
150 silly decomposeActions fetch [email protected]
151 silly decomposeActions extract [email protected]
152 silly decomposeActions preinstall [email protected]
153 silly decomposeActions build [email protected]
154 silly decomposeActions install [email protected]
155 silly decomposeActions postinstall [email protected]
156 silly decomposeActions finalize [email protected]
157 silly decomposeActions refresh-package-json [email protected]
158 silly decomposeActions fetch [email protected]
159 silly decomposeActions extract [email protected]
160 silly decomposeActions preinstall [email protected]
161 silly decomposeActions build [email protected]
162 silly decomposeActions install [email protected]
163 silly decomposeActions postinstall [email protected]
164 silly decomposeActions finalize [email protected]
165 silly decomposeActions refresh-package-json [email protected]
166 silly decomposeActions fetch [email protected]
167 silly decomposeActions extract [email protected]
168 silly decomposeActions preinstall [email protected]
169 silly decomposeActions build [email protected]
170 silly decomposeActions install [email protected]
171 silly decomposeActions postinstall [email protected]
172 silly decomposeActions finalize [email protected]
173 silly decomposeActions refresh-package-json [email protected]
174 silly decomposeActions fetch [email protected]
175 silly decomposeActions extract [email protected]
176 silly decomposeActions preinstall [email protected]
177 silly decomposeActions build [email protected]
178 silly decomposeActions install [email protected]
179 silly decomposeActions postinstall [email protected]
180 silly decomposeActions finalize [email protected]
181 silly decomposeActions refresh-package-json [email protected]
182 silly decomposeActions fetch [email protected]
183 silly decomposeActions extract [email protected]
184 silly decomposeActions preinstall [email protected]
185 silly decomposeActions build [email protected]
186 silly decomposeActions install [email protected]
187 silly decomposeActions postinstall [email protected]
188 silly decomposeActions finalize [email protected]
189 silly decomposeActions refresh-package-json [email protected]
190 silly install executeActions
191 silly doSerial global-install 112
192 verbose correctMkdir /Users/christianemmer/.npm/_locks correctMkdir not in flight; initializing
193 verbose lock using /Users/christianemmer/.npm/_locks/staging-49858fa223067bb7.lock for /Users/christianemmer/concat/node_modules/.staging
194 silly doParallel extract 14
195 silly extract [email protected]
196 silly extract [email protected]
197 silly extract [email protected]
198 silly extract [email protected]
199 silly extract [email protected]
200 silly extract [email protected]
201 silly extract [email protected]
202 silly extract [email protected]
203 silly extract [email protected]
204 silly extract [email protected]
205 silly extract [email protected]
206 silly extract [email protected]
207 silly extract [email protected]
208 silly extract [email protected]
209 silly tarball trying balanced-match@^1.0.0 by hash: sha1-ibTRmasr7kneFk6gK4nORi1xt2c=
210 silly tarball trying [email protected] by hash: sha1-2Klr13/Wjfd5OnMDajug1UBdR3s=
211 silly tarball trying brace-expansion@^1.1.7 by hash: sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==
212 silly tarball trying fs.realpath@^1.0.0 by hash: sha1-FQStJSMVjKpA20onh8sBQRmU6k8=
213 silly tarball trying inherits@2 by hash: sha1-Yzwsg+PaQqUC9SRmAiSA9CCCYd4=
214 silly tarball trying lodash@^4.17.11 by hash: sha512-cQKh8igo5QUhZ7lg38DYWAxMvjSAKG0A8wGSVimP07SIUEK2UO+arSRKbRZWtelMtN5V0Hkwh5ryOto/SshYIg==
215 silly tarball trying [email protected] by hash: sha512-yJHVQEhyqPLUTgt9B83PXu6W3rx4MvvHvSUvToogpwoGDOUQ+yDrR0HRot+yOCdCO7u4hX3pWft6kWBBcqh0UA==
216 silly tarball trying path-is-absolute@^1.0.0 by hash: sha1-F0uSaHNVNP+8es5r9TpanhtcX18=
217 silly tarball trying wrappy@1 by hash: sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=
218 silly tarball trying once@^1.3.0 by hash: sha1-WDsap3WWHUsROsF9nFC6753Xa9E=
219 silly tarball trying inflight@^1.0.4 by hash: sha1-Sb1jMdfQLQwJvJEKEHW6gWW1bfk=
220 silly tarball trying [email protected] by hash: sha512-H1qVYh1MYhEEFLsP97cVKqCGo7KfCyTt6uEWqsTBr9SO84oK9Uwbyd/yCW+6rKJLHksBNUVWZDAjfS+Ccx0Bbg==
221 silly tarball trying [email protected] by hash: sha512-vcfuiIxogLV4DlGBHIUOwI0IbrJ8HWPc4MU7HzviGeNho/UJDfi6B5p3sHeWIQ0KGIU0Jpxi5ZHxemQfLkkAwQ==
222 silly tarball trying metalsmith-concat@latest by hash: sha512-MDIbOwgd0/cRYH7nVT/2pSnLfytIIrhETC/baa5dvjggYWVM419P8JZYE4MLz4eqLWIgfVDO47Lg38QdRVDFig==
223 silly extract balanced-match@^1.0.0 extracted to /Users/christianemmer/concat/node_modules/.staging/balanced-match-be3a5105 (84ms)
224 silly extract brace-expansion@^1.1.7 extracted to /Users/christianemmer/concat/node_modules/.staging/brace-expansion-13b0adb0 (84ms)
225 silly extract path-is-absolute@^1.0.0 extracted to /Users/christianemmer/concat/node_modules/.staging/path-is-absolute-6687f3f8 (83ms)
226 silly extract wrappy@1 extracted to /Users/christianemmer/concat/node_modules/.staging/wrappy-78567798 (82ms)
227 silly extract inflight@^1.0.4 extracted to /Users/christianemmer/concat/node_modules/.staging/inflight-6074e631 (82ms)
228 silly extract once@^1.3.0 extracted to /Users/christianemmer/concat/node_modules/.staging/once-3a83d859 (82ms)
229 silly extract inherits@2 extracted to /Users/christianemmer/concat/node_modules/.staging/inherits-710e3a9d (86ms)
230 silly extract fs.realpath@^1.0.0 extracted to /Users/christianemmer/concat/node_modules/.staging/fs.realpath-f54e9de5 (86ms)
231 silly extract [email protected] extracted to /Users/christianemmer/concat/node_modules/.staging/minimatch-75157db3 (85ms)
232 silly extract metalsmith-concat@latest extracted to /Users/christianemmer/concat/node_modules/.staging/metalsmith-concat-6e751860 (84ms)
233 silly extract [email protected] extracted to /Users/christianemmer/concat/node_modules/.staging/concat-map-8a603632 (89ms)
234 silly extract [email protected] extracted to /Users/christianemmer/concat/node_modules/.staging/glob-d4851790 (85ms)
235 silly extract [email protected] extracted to /Users/christianemmer/concat/node_modules/.staging/async-a9c5d498 (124ms)
236 silly extract lodash@^4.17.11 extracted to /Users/christianemmer/concat/node_modules/.staging/lodash-514f5f9d (280ms)
237 timing action:extract Completed in 284ms
238 silly doReverseSerial unbuild 112
239 silly doSerial remove 112
240 silly doSerial move 112
241 silly doSerial finalize 112
242 silly finalize /Users/christianemmer/concat/node_modules/balanced-match
243 silly finalize /Users/christianemmer/concat/node_modules/concat-map
244 silly finalize /Users/christianemmer/concat/node_modules/brace-expansion
245 silly finalize /Users/christianemmer/concat/node_modules/fs.realpath
246 silly finalize /Users/christianemmer/concat/node_modules/inherits
247 silly finalize /Users/christianemmer/concat/node_modules/lodash
248 silly finalize /Users/christianemmer/concat/node_modules/minimatch
249 silly finalize /Users/christianemmer/concat/node_modules/path-is-absolute
250 silly finalize /Users/christianemmer/concat/node_modules/wrappy
251 silly finalize /Users/christianemmer/concat/node_modules/once
252 silly finalize /Users/christianemmer/concat/node_modules/inflight
253 silly finalize /Users/christianemmer/concat/node_modules/async
254 silly finalize /Users/christianemmer/concat/node_modules/glob
255 silly finalize /Users/christianemmer/concat/node_modules/metalsmith-concat
256 timing action:finalize Completed in 16ms
257 silly doParallel refresh-package-json 14
258 silly refresh-package-json /Users/christianemmer/concat/node_modules/balanced-match
259 silly refresh-package-json /Users/christianemmer/concat/node_modules/concat-map
260 silly refresh-package-json /Users/christianemmer/concat/node_modules/brace-expansion
261 silly refresh-package-json /Users/christianemmer/concat/node_modules/fs.realpath
262 silly refresh-package-json /Users/christianemmer/concat/node_modules/inherits
263 silly refresh-package-json /Users/christianemmer/concat/node_modules/lodash
264 silly refresh-package-json /Users/christianemmer/concat/node_modules/minimatch
265 silly refresh-package-json /Users/christianemmer/concat/node_modules/path-is-absolute
266 silly refresh-package-json /Users/christianemmer/concat/node_modules/wrappy
267 silly refresh-package-json /Users/christianemmer/concat/node_modules/once
268 silly refresh-package-json /Users/christianemmer/concat/node_modules/inflight
269 silly refresh-package-json /Users/christianemmer/concat/node_modules/async
270 silly refresh-package-json /Users/christianemmer/concat/node_modules/glob
271 silly refresh-package-json /Users/christianemmer/concat/node_modules/metalsmith-concat
272 timing action:refresh-package-json Completed in 33ms
273 silly doParallel preinstall 14
274 silly preinstall [email protected]
275 info lifecycle [email protected]~preinstall: [email protected]
276 silly preinstall [email protected]
277 info lifecycle [email protected]~preinstall: [email protected]
278 silly preinstall [email protected]
279 info lifecycle [email protected]~preinstall: [email protected]
280 silly preinstall [email protected]
281 info lifecycle [email protected]~preinstall: [email protected]
282 silly preinstall [email protected]
283 info lifecycle [email protected]~preinstall: [email protected]
284 silly preinstall [email protected]
285 info lifecycle [email protected]~preinstall: [email protected]
286 silly preinstall [email protected]
287 info lifecycle [email protected]~preinstall: [email protected]
288 silly preinstall [email protected]
289 info lifecycle [email protected]~preinstall: [email protected]
290 silly preinstall [email protected]
291 info lifecycle [email protected]~preinstall: [email protected]
292 silly preinstall [email protected]
293 info lifecycle [email protected]~preinstall: [email protected]
294 silly preinstall [email protected]
295 info lifecycle [email protected]~preinstall: [email protected]
296 silly preinstall [email protected]
297 info lifecycle [email protected]~preinstall: [email protected]
298 silly preinstall [email protected]
299 info lifecycle [email protected]~preinstall: [email protected]
300 silly preinstall [email protected]
301 info lifecycle [email protected]~preinstall: [email protected]
302 timing action:preinstall Completed in 2ms
303 silly doSerial build 112
304 silly build [email protected]
305 info linkStuff [email protected]
306 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
307 silly build [email protected]
308 info linkStuff [email protected]
309 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
310 silly build [email protected]
311 info linkStuff [email protected]
312 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
313 silly build [email protected]
314 info linkStuff [email protected]
315 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
316 silly build [email protected]
317 info linkStuff [email protected]
318 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
319 silly build [email protected]
320 info linkStuff [email protected]
321 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
322 silly build [email protected]
323 info linkStuff [email protected]
324 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
325 silly build [email protected]
326 info linkStuff [email protected]
327 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
328 silly build [email protected]
329 info linkStuff [email protected]
330 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
331 silly build [email protected]
332 info linkStuff [email protected]
333 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
334 silly build [email protected]
335 info linkStuff [email protected]
336 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
337 silly build [email protected]
338 info linkStuff [email protected]
339 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
340 silly build [email protected]
341 info linkStuff [email protected]
342 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
343 silly build [email protected]
344 info linkStuff [email protected]
345 silly linkStuff [email protected] has /Users/christianemmer/concat/node_modules as its parent node_modules
346 timing action:build Completed in 2ms
347 silly doSerial global-link 112
348 silly doParallel update-linked 0
349 silly doSerial install 112
350 silly install [email protected]
351 info lifecycle [email protected]~install: [email protected]
352 silly install [email protected]
353 info lifecycle [email protected]~install: [email protected]
354 silly install [email protected]
355 info lifecycle [email protected]~install: [email protected]
356 silly install [email protected]
357 info lifecycle [email protected]~install: [email protected]
358 silly install [email protected]
359 info lifecycle [email protected]~install: [email protected]
360 silly install [email protected]
361 info lifecycle [email protected]~install: [email protected]
362 silly install [email protected]
363 info lifecycle [email protected]~install: [email protected]
364 silly install [email protected]
365 info lifecycle [email protected]~install: [email protected]
366 silly install [email protected]
367 info lifecycle [email protected]~install: [email protected]
368 silly install [email protected]
369 info lifecycle [email protected]~install: [email protected]
370 silly install [email protected]
371 info lifecycle [email protected]~install: [email protected]
372 silly install [email protected]
373 info lifecycle [email protected]~install: [email protected]
374 silly install [email protected]
375 info lifecycle [email protected]~install: [email protected]
376 silly install [email protected]
377 info lifecycle [email protected]~install: [email protected]
378 timing action:install Completed in 2ms
379 silly doSerial postinstall 112
380 silly postinstall [email protected]
381 info lifecycle [email protected]~postinstall: [email protected]
382 silly postinstall [email protected]
383 info lifecycle [email protected]~postinstall: [email protected]
384 silly postinstall [email protected]
385 info lifecycle [email protected]~postinstall: [email protected]
386 silly postinstall [email protected]
387 info lifecycle [email protected]~postinstall: [email protected]
388 silly postinstall [email protected]
389 info lifecycle [email protected]~postinstall: [email protected]
390 silly postinstall [email protected]
391 info lifecycle [email protected]~postinstall: [email protected]
392 silly postinstall [email protected]
393 info lifecycle [email protected]~postinstall: [email protected]
394 silly postinstall [email protected]
395 info lifecycle [email protected]~postinstall: [email protected]
396 silly postinstall [email protected]
397 info lifecycle [email protected]~postinstall: [email protected]
398 silly postinstall [email protected]
399 info lifecycle [email protected]~postinstall: [email protected]
400 silly postinstall [email protected]
401 info lifecycle [email protected]~postinstall: [email protected]
402 timing audit submit Completed in 353ms
403 http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/audits/quick 353ms
404 silly postinstall [email protected]
405 info lifecycle [email protected]~postinstall: [email protected]
406 timing audit body Completed in 0ms
407 silly postinstall [email protected]
408 info lifecycle [email protected]~postinstall: [email protected]
409 silly postinstall [email protected]
410 info lifecycle [email protected]~postinstall: [email protected]
411 verbose lifecycle [email protected]~postinstall: unsafe-perm in lifecycle true
412 verbose lifecycle [email protected]~postinstall: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/christianemmer/concat/node_modules/metalsmith-concat/node_modules/.bin:/Users/christianemmer/concat/node_modules/.bin:/Users/christianemmer/.sdkman/candidates/kotlin/current/bin:/Users/christianemmer/.sdkman/candidates/java/current/bin:/Users/christianemmer/.sdkman/candidates/gradle/current/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/Users/christianemmer/go/bin:/usr/local/opt/imagemagick@6/bin:/usr/local/opt/[email protected]/bin:/Users/christianemmer/.gem/ruby/2.3.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/opt/X11/bin
413 verbose lifecycle [email protected]~postinstall: CWD: /Users/christianemmer/concat/node_modules/metalsmith-concat
414 silly lifecycle [email protected]~postinstall: Args: [ '-c', 'cd example && npm install' ]
415 silly lifecycle [email protected]~postinstall: Returned: code: 1  signal: null
416 info lifecycle [email protected]~postinstall: Failed to exec postinstall script
417 timing action:postinstall Completed in 17ms
418 verbose unlock done using /Users/christianemmer/.npm/_locks/staging-49858fa223067bb7.lock for /Users/christianemmer/concat/node_modules/.staging
419 timing stage:rollbackFailedOptional Completed in 131ms
420 timing stage:runTopLevelLifecycles Completed in 849ms
421 silly saveTree concat
421 silly saveTree └─┬ [email protected]
421 silly saveTree   ├─┬ [email protected]
421 silly saveTree   │ └── [email protected]
421 silly saveTree   ├─┬ [email protected]
421 silly saveTree   │ ├── [email protected]
421 silly saveTree   │ ├─┬ [email protected]
421 silly saveTree   │ │ ├─┬ [email protected]
421 silly saveTree   │ │ │ └── [email protected]
421 silly saveTree   │ │ └── [email protected]
421 silly saveTree   │ ├── [email protected]
421 silly saveTree   │ ├─┬ [email protected]
421 silly saveTree   │ │ └─┬ [email protected]
421 silly saveTree   │ │   ├── [email protected]
421 silly saveTree   │ │   └── [email protected]
421 silly saveTree   │ ├── [email protected]
421 silly saveTree   │ └── [email protected]
421 silly saveTree   └── [email protected]
422 warn enoent ENOENT: no such file or directory, open '/Users/christianemmer/concat/package.json'
423 verbose enoent This is related to npm not being able to find a file.
424 warn concat No description
425 warn concat No repository field.
426 warn concat No README data
427 warn concat No license field.
428 verbose stack Error: [email protected] postinstall: `cd example && npm install`
428 verbose stack Exit status 1
428 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
428 verbose stack     at emitTwo (events.js:126:13)
428 verbose stack     at EventEmitter.emit (events.js:214:7)
428 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
428 verbose stack     at emitTwo (events.js:126:13)
428 verbose stack     at ChildProcess.emit (events.js:214:7)
428 verbose stack     at maybeClose (internal/child_process.js:925:16)
428 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
429 verbose pkgid [email protected]
430 verbose cwd /Users/christianemmer/concat
431 verbose Darwin 18.2.0
432 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--save" "metalsmith-concat"
433 verbose node v8.9.0
434 verbose npm  v6.9.0
435 error code ELIFECYCLE
436 error errno 1
437 error [email protected] postinstall: `cd example && npm install`
437 error Exit status 1
438 error Failed at the [email protected] postinstall script.
438 error This is probably not a problem with npm. There is likely additional logging output above.
439 verbose exit [ 1, true ]

I'm on OSX 10.14.3 with Node v8.9.0.

file paths should be normalized

When using the array syntax for metalsmith-concat (#2), it appears that file paths should be normalized otherwise, I get an error that tells that the file does not exist :

Error: js/jquery-2.1.1.min.js does not exist

And it's right, on windows the file is at js\\jquery-2.1.1.min.js.

File path should be normalized to be OS agnostic.

You can find more information in an article that helps Writing cross-platform Node.js.

High Dependency Vulnerability: minimatch

From npm audit:

┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High          │ Regular Expression Denial of Service                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ minimatch                                                    │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=3.0.2                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ metalsmith-concat                                            │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ metalsmith-concat > minimatch                                │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/118                             │
└───────────────┴──────────────────────────────────────────────────────────────┘

Concatenate outside of directory

can we concatenate files outside of the CWD?

typo in README | metalsmith-concat#javascript

Small typo in the README:

Metalsmith(__dirname)
  .use(concat{    // missing '(' after concat
    files: 'styles/**/*.css',
    output: 'styles/app.css'
  }));  // extra colon here
  .build();

Thanks for the plugin btw! awsome!

mix array and minimatch

I agree that #1 can solve some problems when files order might matter, we can then hard-code an array to specify the concatenation order.

But my case is slightly different, and #1 and #2 do not fit in my case. I'm using many js library. I'm using Bootstrap, I'm then also using JQuery.

I need to concat JQuery before Boostrap (which is made of many many small files) and then concat all my other files. I don't want to hard-code all my js files (I have more than 20 files, and these files may vary).

I want to be able to mix array and minimatch to get a power configuration, such as this one :

.use(concat({ // concat javascript
    files: ['js/jquery-2.1.1.min.js', 'js/bootstrap/*.js', 'js/**/*.js'],
    output: 'js/app.js'
}))

This way, I'm sure to concat JQuery in first, then all Bootstrap js, then my custom js.

Obviously, files which were already concatenated before sould not be concatenated again with following expressions (ie. JQuery and Bootstrap js should not be concatenated again by 'js/**/*.js').

This would make metalsmith-concat realy more powerful than it is today.

We could then build concatenated js from scratch and then being able to customize Boostrap easily !

Path Separator is Mixed on Windows

On Windows (process.platform === 'win32') the path separator is \, not / as used here:

metalsmith-concat/index.js

Line 67 in 4a93c96

return path.replace(/[/\\]+/g, '/');

Looks like this is attempting to "fix" Windows to be Unix-like, but this is wrong, Metalsmith does use \ path separators in the files object.

support sourcemaps when concatenating

@ksmithut said:

In regards to sourcemap support, metalsmith-concat should support it. If it takes input files and generates a different file, it should support sourcemaps (although it doesn't appear they do as you mentioned). Grunt/Gulp plugins support it, so metalsmith plugins should as well.

Files deleted when paired with live reload.

I'm having a problem when pairing this pluging with the livereload functionality of metalsmith-watch.

I have a build which concats my styles to create styles/app.css. When I build, this works fine. I also have metalsmith watch enabled with livereload. When livereload triggers with a file (for example index.html), it pushes just that file through the build. This means that when the build reaches the concat step, there are no css files in the build, so it overrides app.css with an empty file.

I've pushed a branch where I recreated this here.

Another problem I foresee is that if I have two css files being concat, and I change just one, then the build would overwrite the output file with a new file that contains only one set of styles.

Let me know if you think this is more of a bug for the metalsmith-watch team, though my guess would be here.

Notify in documentation the base path

Notify user in documentation that the concat plugin ('file' and 'output') is based on the destination path

writing files with strings vs Buffers?

Hey @aymericbeaumet - I was passing some metalsmith-concatenated files to metalsmith-layouts, and nothing was getting generated.

Turns out that metalsmith-layouts was silently failing (which is a separate issue), because it was expecting a utf-8 encoded Buffer, but the contents of the newly metalsmith-concatenated file was a string.

Just wanted to check here and see, is that expected? My experience with Metalsmith is that file contents are stored as Buffers, and it seems like metalsmith-concat is spitting out file contents as strings.

If this is intended, no worries, and if not, happy to take a whack at it and send a PR your way, just let me know.

Thanks!

Multiple output files

Can the script handle multiple output files?

e.g.

{
[{
files:["js1.js","js2.js"],
output:"path/to/file.js"
},{
files:["jquery.js","jquery-ui.js"],
output:"path/to/jquery.bundle.js"
}]
}

Allow adding of a specific array of files

Rather than just a glob.

For js files where order might matter, it would be nice to just throw in a hard-coded array, instead of pattern. Seems when I do that, I end up with a concatenited file, that contains the entire directories content (6.4 MB!)

    "metalsmith-concat": {
      "files": ["jspath/a_filename.js","jspath/another_filename.js"],
      "output": "js/scripts.js"
    }

Make overwrite check optional

I got Error: The file "XZY" already exists rejection if I try to concat some files into an existing one.

However, in my use case this is the intended behaviour. Is it possible to add an option like disableOverwriteCheck: true to make this check optional?

Getting an error when src directory contains same name of file build should concat to

I have a file app.scss in my src.

I want to combine all compiled *.css from *.scss in src to the file app.css in build.

When I use metalsmith-concat, it complains that app.css already exists, even though it should not exist in build. It only exists as app.scss in src.

Error: The file "app.css" already exists
    at Ware.<anonymous> (/Users/devin/Projects/rebelmail-website/node_modules/metalsmith-concat/lib/index.js:42:13)
    at Ware.<anonymous> (/Users/devin/Projects/rebelmail-website/node_modules/metalsmith/node_modules/ware/node_modules/wrap-fn/index.js:45:19)
    at next (/Users/devin/Projects/rebelmail-website/node_modules/metalsmith/node_modules/ware/lib/index.js:85:20)
    at /Users/devin/Projects/rebelmail-website/node_modules/metalsmith/node_modules/ware/node_modules/wrap-fn/index.js:121:18
    at /Users/devin/Projects/rebelmail-website/node_modules/metalsmith-sass/node_modules/async/lib/async.js:52:16
    at done (/Users/devin/Projects/rebelmail-website/node_modules/metalsmith-sass/node_modules/async/lib/async.js:248:21)
    at /Users/devin/Projects/rebelmail-website/node_modules/metalsmith-sass/node_modules/async/lib/async.js:44:16
    at Object.callback (/Users/devin/Projects/rebelmail-website/node_modules/metalsmith-sass/lib/index.js:100:13)
    at options.success (/Users/devin/Projects/rebelmail-website/node_modules/metalsmith-sass/node_modules/node-sass/lib/index.js:293:32)

Files deleted when paired with live reload.

Empty dist file

This plugin is not working anymore. The dist file is generated but remains empty.

Allow Concatination of files outside src

Allowing concatinating files from outside the source directory would be nice.

Lumens

Vadim February 21, 2018 19:06

Hello! Faced such a problem. I can not send coins from my wallet writes such a mistake ..
{
"type": "https://stellar.org/horizon-errors/transaction_failed",
"title": "Transaction Failed",
"status": 400,
"detail": "The transaction failed when submitted to the stellar network. The extras.result_codes field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html",
"instance": "horizon-001a/71LV2KXh2A-72849508",
"extras": {
"envelope_xdr": "AAAAAOt0auvBKc3j0AP633hqvJktLnqNtmmXgn10O/KJPFLEAAAAZADzw0MAAAABAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAAq2OR6BMg2SaeqkLqwpebz+1JZnhKV4eqluP9fJOubPMAAAAAAAAAAA7msoAAAAAAAAAAAYk8UsQAAABA56SIUdNMxvVJoLVt3orBQxa8upgS3y+x2ak+ve3s/2rNQOfn4rXDijW2VkXStnouk7vG1878P50GzieSMLjXDA==",
"result_codes": {
"transaction": "tx_failed",
"operations": [
"op_bad_auth"
]
},
"result_xdr": "AAAAAAAAAGT/////AAAAAf////8AAAAA"
}
}.
the purse 788 lumens How do I get my money back?

Add sort option

I'm not sure where I got the impression that if my css directory contained 01_foo.css and 02_bar.css. then metalsmith-concat would reliably produce the equivalent of cat 01_foo.css 02_bar.css. But apparently it does not. This makes the plugin hard to use in cases where you are trying to combine things that have dependencies without having to pass an array to the plugin.

It seems like a simple lexicographic sort after locating the files and before concatenating them wouldn't break anything and would enable this use pattern.

Simplify paths

make sure complex paths like a///b////c are properly simplified to a/b/c

Glob in array

Good to know, glob are not taken in arrays.

Can no longer be installed due to npm-shrinkwrap 5.4.0 dependency

I’ve just started working on a project that uses metalsmith-concat and can’t seem to install it because of the dependency on npm-shrinkwrap 5.4.0. That version of shrinkwrap depends on an older version of read-json that is no longer available (not sure if any relation to Azer Koçulu unpublishing of a bunch of modules yesterday, read-json among them).

At any rate, npm-shrinkwrap 5.4.1 appears to no longer depend on read-json and is installable for me. So I think the issue would be resolved by simply bumping the dependency up to 5.4.1 in package.json.

metalsmith-concat fails to install with npm 2.3.0

metalsmith-concat fails to install with npm 2.3.0 :

>npm install metalsmith-concat
npm WARN engine [email protected]: wanted: {"node":">=0.8","npm":"1"} (current: {"node":"0.12.7","npm":"2.3.0"})
npm WARN package.json [email protected] No repository field.
npm ERR! cb() never called!

>npm --version
2.3.0

Everything goes well after updating npm from version 2.3.0 to 2.14.0

package.json description says minify css files

not really an issue but while using your source as an example I noticed that your package.json has a 'wrong' description.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.