[FOLIO-1031] Prevent minification of JS code for "testing" stripes builds Created: 16/Jan/18 Updated: 15/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | Continuous Integration |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ci, sprint43, sprint44, sprint45 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 15 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
JS errors in the browser console are obfuscated by code minification. We could set NODE_ENV=development for the "testing" builds to make things easier to debug. "snapshot" builds should continue to use minified code. |
| Comments |
| Comment by Wayne Schneider [ 27/Apr/18 ] |
|
Command should be: $ yarn build <output_directory> --nominify or something like that. The --nominify option is not yet available |
| Comment by Matthew Jones [ 03/May/18 ] |
|
Wayne Schneider, this has been merged. The new option is --no-minify. By convention, the no- prefix will negate boolean options in both command frameworks used by stripes-core and stripes-cli. When omitted, minification will occur. Using folio-testing-platform's package.json script: yarn build <output_directory> --no-minify Using the CLI: stripes build <stripes_config> --output <output_directory> --no-minify |