Uploaded image for project: 'Appcelerator CLI'
  1. Appcelerator CLI
  2. CLI-1108

Move from using workspace-clean and cache clean to using npm update


    • Type: Story
    • Status: Resolved
    • Priority: None
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:


      Attempt to make the build faster by not performing as aggressively a clean. The concern:

      You could get an old version of a dependency. You might be able to use https://docs.npmjs.com/cli/update, but not sure that’s reliable, since it only does top-level packages by default. That would definitely be an issue for me in the CLI since I’d possibly be shrinkwrapping an older version of a sub-dependency. An example where that might have an effect:

      Note: I have not tested this, and I think testing it might be the only way to ascertain for sure the behavior, since the docs aren’t super-clear.


      • I update appc-registry-sdk from 1.0.0 to 1.0.1.
      • I also bump arrow-admin from 2.0.0 to 2.0.1
      • arrow-admin has a dependency of appc-registry-sdk: “~1.0.0”
      • arrow has a dependency of arrow-admin: “2.0.0”

      If I npm install inside arrow-admin, and don’t clean, assuming I’ve already installed version 1.0.0 of appc-registry-sdk, I don’t think it would update it. Npm update should update it, however.

      If I npm install inside arrow, and don’t clean, assuming I’ve already installed version 2.0.0 of arrow-admin, it should not update arrow-admin or appc-registry-sdk. NPM update, however, would only update arrow-admin (top-level dependency) and NOT appc-registry-sdk




            • Assignee:
              ingo Ingo Muschenetz
            • Watchers:
              2 Start watching this issue


              • Created:

                Git Source Code