1. 02 Feb, 2018 1 commit
    • Ian Sutherland's avatar
      Named asset import for SVG files (#3907) · d0e17316
      Ian Sutherland authored
      * Add named asset import for svg files via babel plugin and webpack loader.
      
      * Fix failing e2e test
      
      * Switched to svgr loader
      
      * Updated SVG component test
      
      * Disable named asset import plugin in test environment
      
      * Added tests for including SVG in CSS
      
      * Update tests
      
      * Moved babel plugin config into webpack config
      d0e17316
  2. 17 Jan, 2018 1 commit
    • Ro Savage's avatar
      Add support for CSS Modules with explicit filename (#2285) · fc7c9915
      Ro Savage authored
      * Add css modules with [name].modules.css file convention
      
      * Add e2e for CSS Modules
      
      * Updated based on feedback
      
      * Change css modules class name to be deterministic and fix licences
      
      * Update css modules class naming convention
      fc7c9915
  3. 09 Jan, 2018 1 commit
  4. 26 Sep, 2017 1 commit
  5. 28 Jun, 2017 1 commit
  6. 14 May, 2017 1 commit
  7. 08 May, 2017 1 commit
  8. 05 May, 2017 1 commit
  9. 25 Apr, 2017 1 commit
  10. 15 Apr, 2017 1 commit
  11. 07 Mar, 2017 1 commit
  12. 06 Mar, 2017 1 commit
  13. 15 Feb, 2017 1 commit
  14. 10 Feb, 2017 1 commit
    • Joe Haddad's avatar
      Add `PUBLIC_URL` env variable for advanced use (#937) (#1504) · 613b584f
      Joe Haddad authored
      * Add `PUBLIC_URL` env variable for advanced use (#937)
      * Add support for `PUBLIC_URL` env variable
      * Remove unnecessary duplications
      * Simplify served path choice logic
      * Honor PUBLIC_URL in development
      * Add e2e tests
      
      Enables serving static assets from specified host.
      613b584f
  15. 08 Feb, 2017 1 commit
  16. 30 Jan, 2017 2 commits
  17. 23 Jan, 2017 1 commit
    • Fabrizio Castellarin's avatar
      Use a more sophisticated template for end-to-end testing. (#1187) · 9099570b
      Fabrizio Castellarin authored
      * Use a more sophisticated template for end-to-end testing.
      
      * Not publish integration tests to npm
      
      * Use "commander" for  cli argv handling
      
      * Handle different scripts version forms and exits without a name given
      
      * Prepare the commands for testing with a template
      
      * Fix dev "template" path
      
      * Add various features to test
      
      * Test various features separately
      
      * Test language features
      
      * Comment unused e2e.sh lines
      
      * Add "development" tests
      
      * Test environment variables
      
      * Test webpack plugins
      
      * Replace kitchensink README
      
      * Switch integration tests from jest to mocha
      
      * Use `fs-extra`
      
      * Use the correct folders
      
      * Do some cleanup
      
      * Print a better message for `--template`
      
      * Test `npm start` with and without https
      
      * Separate fast e2e testing from kitchensink testing
      
      * Hide `--internal-testing-template` (former `--template`) CLI option
      9099570b