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

npmconf causing errors when resolving plugins


    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: 7.0.1-master.1
    • Component/s: Core
    • Labels:
    • Story Points:
    • Sprint:
      2017 Sprint 25 Tooling


      The following error appears when running arrow tests. (which exec an appc run -l trace from a generated project) I never fully traced down the location of the issue in npmconf, but running the app generated by the tests directly does not show this error, so it's possibly something to do with the cwd.

      invalid config https-proxy=undefined
      invalid config Must be a full url with 'http://'
      invalid config loglevel="notice"
      invalid config proxy=undefined
      invalid config Must be a full url with 'http://'
      2017-12-11T12:57:53.912Z | ERROR  | Error: ENOENT: no such file or directory, open 'C:\Users\ahurst\AppData\Local\Temp\arrow-tmp\arrow_test_1512997071265.36.229339544800695\undefined'

      These config options which are causing the error are npm defaults, however, and not set directly by me. The error is being thrown by the npmconf module, which is now deprecated with warnings of Do not use this package..

      While the suggested alternative is to use npm for this check, I don't feel like having npm as a dependency is a good idea, and I don't think that it is expected. Other packages seem to be using https://github.com/kevva/npm-conf instead.

      I've created a branch which uses npm-conf instead of npmconf and this no longer throws errors or emits warnings.




            • Assignee:
              emerriman Eric Merriman
              ahurst Alasdair Hurst
            • Watchers:
              3 Start watching this issue


              • Created:

                Git Source Code