dmpopidor / lib / assets /
@Jose Lloret Jose Lloret authored on 18 Sep 2017
..
fonts Resolve merge conflicts. DMPRoadmap/roadmap#587 8 years ago
images tinymce refactoring for notes using JS. DMPRoadmap/roadmap#571 8 years ago
javascripts guidances_notes layout according to bootstrap. DMPRoadmap/roadmap#562 8 years ago
stylesheets DMPRoadmap/roadmap#562 8 years ago
videos/index.files/ html5video tinymce refactoring for notes using JS. DMPRoadmap/roadmap#571 8 years ago
.eslintrc.json added data-validation for emails at plan details. DMPRoadmap/roadmap#559 8 years ago
.keep front-end dependencies handled through npm. DMPRoadmap/roadmap#551 8 years ago
README.md is module and travis configuration tweaked. DMPRoadmap/roadmap#601 8 years ago
karma.conf.js 1. click ariatiseForm preventDefault only once now 8 years ago
package-lock.json Boostrapped the create plan page. DMPRoadmap/roadmap#632 8 years ago
package.json 1. click ariatiseForm preventDefault only once now 8 years ago
webpack.config.js Boostrapped the create plan page 8 years ago
webpack.karma.config.js is module and travis configuration tweaked. DMPRoadmap/roadmap#601 8 years ago
README.md

Set up

We use WebPack to pre-compile all our assets. Before executing any bundling, please make sure that all the dependencies are installed first by typing:

npm install

within lib/assets

Assets Bundling

We have set up two environments, one for development which watching for changes at any .js or .css file to pre-compile on the fly and another for production. For a development environment, i.e. if the developer is making changes, please type:

npm run bundle

and for production, please type:

npm run bundle -- -p

Note, the above commands have to run within lib/assets directory.

Testing

We use jasmine to write unit tests together with karma for testing in real browser our functionality. Please type the following command to execute every test for JavaScript modules.

npm test