Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-1877

Separation of devDependencies and dependencies in package.json

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • 3.3.0
    • 3.2.1
    • Gulp
    • Hide
      1. Create a new project and clone the repository in it.
      2. Run npm install and check that all the dependencies (including gulp, gulp-clean-css, gulp-concat, gulp-rename and gulp-sass) are installed.
      3. Run bower install.
      4. Run gulp. Check that the build files are created in the project.
      Show
      Create a new project and clone the repository in it. Run npm install and check that all the dependencies (including gulp, gulp-clean-css, gulp-concat, gulp-rename and gulp-sass) are installed. Run bower install . Run gulp . Check that the build files are created in the project.
    • MOODLE_32_STABLE
    • MOODLE_33_STABLE
    • Moodle Mobile 3.3.0

      Currently there is no clear separation between which packages are under dependencies and devDependencies (see this for a discussion regarding their difference).
      According to my understanding, only the front-end libraries that the front-end client (ionic-bower, and other bower components) goes under the dependencies tag, while all the existing once should be placed under devDependencies.

      All packages should be placed under devDependencies. When MOBILE-1830 is solved, bower packages should be placed under dependencies.

            dpalou Dani Palou
            martinmine Martin Storø Nyfløtt
            Pau Ferrer Pau Ferrer
            Juan Leyva Juan Leyva
            Juan Leyva Juan Leyva
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.