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

    vueCompiler: true does not seem to include Vue runtime + compiler

    Help
    compiler-build vue vuecompiler
    1
    3
    774
    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.
    • J
      jelices last edited by

      Hello,

      I am trying to use v-runtime-template (https://github.com/alexjoverm/v-runtime-template) or any other way of using Vue templates that are not pre-compiled. I have activated the option in quasar.conf.js:

      build: {
        vueCompiler: true
      }
      

      That seems like the only necessary step to bundle both Vue runtime + compiler, but it does not seem to work. For instance, see https://quasar.dev/quasar-cli/quasar-conf-js#Property%3A-build and https://github.com/alexjoverm/v-runtime-template/issues/16.

      When I try to run the code with quasar dev, I get the error:

      [Vue warn]: You are using the runtime-only build of Vue where the template compiler is not available. Either pre-compile the templates into render functions, or use the compiler-included build.
      

      I don’t think the problem is related to v-runtime-template as the message is the generic Vue error for the case when the compiler is not present.

      I have upgraded to the latest Quasar version of everything but the problem persists.

      Is there anything else I should be doing? Thank you in advance!

      1 Reply Last reply Reply Quote 0
      • J
        jelices last edited by

        I have tried creating a Quasar project from scratch and using the demo project, install v-runtime-template and try a trivial example. That works, so the problem seems to be related with my particular project. I have tried removing both the node_modules directory and the package-lock.json file and run npm install but it does not help. Any ideas will be appreciated. Thank you!

        1 Reply Last reply Reply Quote 0
        • J
          jelices last edited by

          Finally I have used a quasar.conf.js from a new blank project generated with the latest CLI and moved all specifics from the former conf to the new one. Both conf files are different and I am not sure what has done it. But now the compiler option works. Seems like using a conf file from an old Quasar version (mine probably started with v0.17) breaks something with newer Quasar versions.

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