speeding up build on windows - Failed to parse file #2154

Activity

1. JonCatmull commented on Nov 28, 2017

   

   JonCatmull

   on Nov 28, 2017

   Author

   More actions

   The reason I'm trying to speed up the build is my build time has gone up massively and I'm not sure why. It used to be a few seconds and now it is consistently 1.6 mins.

   Latest compile:

   [10:54:27] Starting 'build.dev'...
   [10:54:27] Starting 'initialize'...
   [10:54:27] Starting 'noop'...
   [10:54:27] Finished 'noop' after 105 μs
   [10:54:27] Finished 'initialize' after 901 μs
   [10:54:27] Starting 'clean.once'...
   [10:54:27] Skipping clean on rebuild
   [10:54:27] Finished 'clean.once' after 198 μs
   [10:54:27] Starting 'build.assets.dev'...
   [10:54:27] Finished 'build.assets.dev' after 157 μs
   [10:54:27] Starting 'build.fonts'...
   [10:54:27] Finished 'build.fonts' after 18 ms
   [10:54:27] Starting 'build.html_css'...
   [10:54:28] Finished 'build.html_css' after 1.01 s
   [10:54:28] Starting 'build.js.dev'...
   [10:56:03] Finished 'build.js.dev' after 1.57 min
   [10:56:03] Starting 'build.index.dev'...
   [10:56:03] gulp-inject 3 files into index.html.
   [10:56:03] gulp-inject 5 files into index.html.
   [10:56:03] gulp-inject 6 files into index.html.
   [10:56:03] Finished 'build.index.dev' after 68 ms
   [10:56:03] Starting 'sw.manifest.static'...
   [10:56:03] Finished 'sw.manifest.static' after 445 ms
   [10:56:03] Finished 'build.dev' after 1.6 min
   [BS] Reloading Browsers...
   
2. vyakymenko commented on Feb 26, 2018

   

   vyakymenko

   on Feb 26, 2018

   Last edited by vyakymenko

   Contributor

   More actions

   Hello @JonCatmull , please install TypeScript npm install typescript -g and try again.
3. vyakymenko commented on Mar 2, 2018

   

   vyakymenko

   on Mar 2, 2018

   Contributor

   More actions

   @JonCatmull , still existing issue?
4. ComFreek commented on Mar 3, 2018

   

   ComFreek

   on Mar 3, 2018

   Last edited by ComFreek

   More actions

   I once had the same suspicious "Failed to parse file..." error after having run tsc (without --project tsconfig.json if I remember correctly). The solution was to delete every .js and .js.map files generated by that tsc, and to always use the npm run build.dev/prod build commands instead of tsc in this seed. But beware, only delete .js files for which there exist corresponding .ts files, i.e. there are still some raw JS-only scripts in this seed.

   Somehow the tsconfig.json in this seed interferes with the remaining build process.
5. JonCatmull commented on Mar 5, 2018

   

   JonCatmull

   on Mar 5, 2018

   Author

   More actions

   Apologies I will test try these 2 commands today and let you know