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 Edge points to v0.14 beta now

    Announcements
    3
    6
    2306
    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.
    • rstoenescu
      rstoenescu Admin last edited by

      Hi All,

      If you are using edge version, please switch to latest official v0.13.10 release instead. Edge is becoming v0.14 and due to tree shaking it will break your app.

      Thank you.

      1 Reply Last reply Reply Quote 3
      • S
        smakinson last edited by

        Attempting to start a new project now with 0.14 and here is what I see if I

        quasar init app_name
        cd app_name
        npm install
        rm -rf node_modules/quasar-framework
        npm i --save git+https://git@github.com/quasarframework/quasar-edge.git

        I see this
        “UNMET PEER DEPENDENCY quasar-extras@0.x”

        quasar dev

        In the js console I see:

        “[Vue warn]: Unknown custom element: <q-layout>”
        “[Vue warn]: Unknown custom element: <q-toolbar-title>”

        [HMR] bundle has 2 warnings
        client.js?7955:161 ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./src/components/Index.vue
        45:32-37 "export ‘Utils’ was not found in ‘quasar’
        ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./src/components/Index.vue
        49:34-39 "export ‘Utils’ was not found in ‘quasar’
        “Uncaught TypeError: Cannot read property ‘dom’ of undefined”

        If I then run:
        npm install quasar-extras --save
        quasar dev

        The unmet dependency is fixed, but I see the same things in the console.

        Just checking to see if you are aware of these or if I’m taking the wrong path to using the beta.

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

          I just noticed the other post mentioned the extras: http://forum.quasar-framework.org/topic/507/v0-14-beta-important-notice

          And I see I have “quasar-extras”: “0.0.7” after installing it.

          1 Reply Last reply Reply Quote 1
          • S
            spectrolite last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • S
              spectrolite last edited by spectrolite

              @smakinson you should use the beta template for init
              first make sure you have the latest quasar-cli version installed : npm install -g quasar-cli
              then use this to start your project:

              quasar init default#beta app_name
              

              the rest of your procedure looks good and should yield a functional project.

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

                Ah thanks for that! I did update the cli first, but did not notice I needed default#beta.

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