Skip to content

Scripts

Jump to bottom
Christopher Haugen edited this page Nov 7, 2017 · 3 revisions

Why not Gulp or Grunt?

Task runners like Gulp or Grunt tend to rely on packages that are specifically designed to make existing packages compatible with the task runner's framework. These gulp/grunt packages can easily become obsolete when the corresponding package is updated. Dealing with the parent packages directly gives us full control in how the application builds without worrying about dependency issues.

Scripts will be found in the scripts.js file located in the config folder.

Main scripts:

  • npm start
    • webpack builds => tree-shakes => bundles application
    • starts webpack-dev-server on http://localhost:8080
  • npm prod
    • webpack builds => tree-shakes => bundles => compresses application
    • starts node server on http://localhost:8443
  • npm test
    • compiles server side and starts jasmine tests on spec and integration api files
    • karma/webpack compiles client and starts client side tests
  • npm e2e
    • webpack builds => tree-shakes => bundles application
    • runs protractor e2e tests
  • npm e2e:prod
    • webpack builds => tree-shakes => bundles => compresses application
    • runs protractor e2e tests in production mode
  • npm deploy:heroku (mongodb)
    • webpack builds => tree-shakes => bundles => compresses application
    • prepares git => pushes to heroku remote
Clone this wiki locally