Wanted versions confusion



  • I have a project that I have been working on for over a year, and along the way I have upgraded to the latest quasar versions each time they are available. But it seems the versions of various similar items in this older project vs a brand new quasar project are different, and I am not sure why, and whether it is safe to force update some of those. For example, running npm outdated on my old project gives me the following result:

    Package                      Current  Wanted  Latest  Location
    @kazupon/vue-i18n-loader       0.4.1   0.4.1   0.5.0  oldproject-ui
    @vue/eslint-config-standard    4.0.0   4.0.0   5.1.2  oldproject-ui
    babel-eslint                  10.0.3  10.1.0  10.1.0  oldproject-ui
    draggabilly                    2.2.0   2.3.0   2.3.0  oldproject-ui
    eslint                        5.16.0  5.16.0   7.1.0  oldproject-ui
    eslint-loader                  2.2.1   2.2.1   4.0.2  oldproject-ui
    eslint-plugin-vue              5.2.3   5.2.3   6.2.2  oldproject-ui
    vue-i18n                       7.8.1   7.8.1  8.17.7  oldproject-ui
    

    Whereas the newly created test project (with axios, eslint standard, i18n options selected) gives me this result:

    Package        Current  Wanted  Latest  Location
    axios           0.18.1  0.18.1  0.19.2  testing
    eslint           6.8.0   6.8.0   7.1.0  testing
    eslint-loader    3.0.4   3.0.4   4.0.2  testing
    

    So the newer create one has installed later versions (but still not the latest) for some things (the three above) and actually the latest version of vue-i18n (v8.17.7) whereas my project above has an earlier version “wanted” which I don’t know why. Is it safe to force update to the later versions? How can I tell? And is it normal that these versions would not be updated when updating quasar?



  • And just in case it matters, here are the results of quasar info for the OLD project:

    Operating System - Darwin(19.4.0) - darwin/x64
    NodeJs - 12.16.3
    
    Global packages
      NPM - 6.14.4
      yarn - Not installed
      @quasar/cli - 1.0.7
      cordova - 8.0.0
    
    Important local packages
      quasar - 1.11.3 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
      @quasar/app - 1.8.10 -- Quasar Framework local CLI
      @quasar/extras - 1.8.1 -- Quasar Framework fonts, icons and animations
      vue - 2.6.10 -- Reactive, component-oriented view layer for modern web interfaces.
      vue-router - 3.2.0 -- Official router for Vue.js 2
      vuex - 3.4.0 -- state management for Vue.js
      electron - Not installed
      electron-packager - Not installed
      electron-builder - Not installed
      @capacitor/core - Not installed
      @capacitor/cli - Not installed
      @capacitor/android - Not installed
      @capacitor/ios - Not installed
      @babel/core - 7.9.6 -- Babel compiler core.
      webpack - 4.43.0 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
      webpack-dev-server - 3.11.0 -- Serves a webpack app. Updates the browser on changes.
      workbox-webpack-plugin - 4.3.1 -- A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.
      register-service-worker - 1.7.1 -- Script for registering service worker, with hooks
      typescript - 3.8.3 -- TypeScript is a language for application scale JavaScript development
    
    Quasar App Extensions
      @quasar/quasar-app-extension-icon-genie - 1.1.3 -- A Quasar CLI Extension for Making All Your Icons
    

    And for the new TEST project:

    Operating System - Darwin(19.4.0) - darwin/x64
    NodeJs - 12.16.3
    
    Global packages
      NPM - 6.14.4
      yarn - Not installed
      @quasar/cli - 1.0.7
      cordova - 8.0.0
    
    Important local packages
      quasar - 1.11.3 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
      @quasar/app - 1.8.10 -- Quasar Framework local CLI
      @quasar/extras - 1.8.1 -- Quasar Framework fonts, icons and animations
      vue - 2.6.11 -- Reactive, component-oriented view layer for modern web interfaces.
      vue-router - 3.2.0 -- Official router for Vue.js 2
      vuex - 3.4.0 -- state management for Vue.js
      electron - Not installed
      electron-packager - Not installed
      electron-builder - Not installed
      @capacitor/core - Not installed
      @capacitor/cli - Not installed
      @capacitor/android - Not installed
      @capacitor/ios - Not installed
      @babel/core - 7.9.6 -- Babel compiler core.
      webpack - 4.43.0 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
      webpack-dev-server - 3.11.0 -- Serves a webpack app. Updates the browser on changes.
      workbox-webpack-plugin - 4.3.1 -- A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.
      register-service-worker - 1.7.1 -- Script for registering service worker, with hooks
      typescript - 3.8.3 -- TypeScript is a language for application scale JavaScript development
    
    Quasar App Extensions
      *None installed*
    


  • Can anyone offer me any guidance here?



  • Well, I just upgraded everything by hand to match versions setup by latest quasar, fixed a bunch of new missing dependencies manually, and then went through and dealt with a ton of new eslint messages. Everything seems to work except for an odd babel-eslint error (in version 10.1.0) about not being able to read prop range of null. There is a lot of discussion on github about it, but I was able to at least turn off messages about it (in eslintrc.js) using

        'template-curly-spacing' : 'off',
        indent: [
          'warn', 2,
          { ignoredNodes: ['TemplateLiteral'], 'SwitchCase': 1 }
        ],
    

    Hope this helps anyone else out there who might be wondering about similar oddities…


Log in to reply