No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    $ quasar dev not working

    Help
    dev not working problem quasar
    5
    5
    11555
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      cheesy last edited by cheesy

      Hi there.
      I have a problem whit quasar when I run: $ quasar dev I get the following output in terminal:

       app:dev Running: Mode [ SPA ] with [ MAT ] theme +0ms
      
       app:quasar-conf Reading quasar.conf.js +816ms
       app:dev Checking listening address availability (192.0.0.10:8080)... +4ms
       app:quasar-conf Generating Webpack config +13ms
       app:quasar-conf Extending Webpack config +24ms
       app:generator Generating Webpack entry point +16ms
       app:dev-server Booting up... +4ms
      
      Build completed in 11.943s
      

      When it should be something like:

       app:quasar-conf Reading quasar.conf.js +816ms
       app:dev Checking listening address availability (192.0.0.10:8080)... +4ms
       app:quasar-conf Generating Webpack config +13ms
       app:quasar-conf Extending Webpack config +24ms
       app:generator Generating Webpack entry point +16ms
       app:dev-server Booting up... +4ms
      
      Build completed in 11.943s
      
      
      
       DONE  Compiled successfully in 11721ms                                                        6:12:27 PM
      
       I  App [SPA with MAT theme] at http://192.0.0.10:8080/
      

      I am using a linux desktop enviroment (Ubuntu 18.04)

      System Information as displayed by the: $ quasar info command:

      Operating System        	Linux(4.15.0-24-generic) - linux/x64
      NodeJs                  	10.4.1
      
      Global packages         	
        NPM                   	6.1.0
        yarn                  	Not installed
        quasar-cli            	0.16.4
        vue-cli               	2.9.6
        cordova               	Not installed
      
      Important local packages	
        quasar-cli            	0.16.4	(Quasar Framework CLI)
        quasar-framework      	0.16.0	(Build responsive websites, PWAs, hybrid mobile apps and Electron apps, all simultaneously using same codebase)
        quasar-extras         	2.0.2	(Quasar Framework fonts, icons and i18n.)
        vue                   	2.5.16	(Reactive, component-oriented view layer for modern web interfaces.)
        vue-router            	3.0.1	(Official router for Vue.js 2)
        vuex                  	3.0.1	(state management for Vue.js)
        electron              	Not installed
        electron-packager     	Not installed
        electron-builder      	Not installed
        @babel/core           	7.0.0-beta.49	(Babel compiler core.)
        webpack               	4.9.1	(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.1.4	(Serves a webpack app. Updates the browser on changes.)
        workbox-webpack-plugin	3.2.0	(A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.)
      
      Networking              	
        Host                  	[EDITED]
        enp1s0                	192.0.0.248
        wlp2s0                	192.0.0.10
      

      I have:

      1. Checked that the port 8080 is free
      2. Check if there is a new version of vue-cli or quasar-cli
      3. Check quasar.conf.js for erros
      4. Try quasar clean and quasar dev again

      Any other ideeas?

      1 Reply Last reply Reply Quote 1
      • J
        JaredThirsk last edited by JaredThirsk

        I ran into a similar problem.

        Tried ‘quasar build’, and it spit out some compile errors at me, though not in the usual way – it was post-processed vue template.

        1 Reply Last reply Reply Quote 1
        • B
          boidcom last edited by

          This happens to me if I have more than one root element in a vue component. It used to throw an error, the latest version of quasar will just freeze like this. When you run quasar build, then you will see the correct errors to resolve.

          1 Reply Last reply Reply Quote 0
          • S
            shisht last edited by

            This happens to me as well when is used template tag inside root template tag, just like this

            <template>
            <div class="demo">
              <template v-if="cond">
                <h1>Hello world</h1>
              </template>
              <template v-else>
                <h1>No Hello world</h1>
              </template>
            </div>
            <template>
            
            1 Reply Last reply Reply Quote 1
            • K
              kyriediculous last edited by

              running build will indeed give the error, quite annoying though 😃

              1 Reply Last reply Reply Quote 0
              • First post
                Last post