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

    Unable to migrate to v1

    Help
    2
    5
    159
    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
      Cochonours last edited by

      As the v1 seemed to be ready, and I saw a few components I would like to use there, I decided to upgrade my project but am stuck with errors everywhere…

      I had been using vue cli 3 without problems until now.

      My current package.json:

        "dependencies": {
          "@quasar/extras": "^1.1.2",
          "quasar": "^1.0.0-rc.3",
          "quasar-cli": "^0.17.25",
          "register-service-worker": "^1.5.2",
          "vue": "^2.5.22",
      ...
        "devDependencies": {
          "@quasar/app": "^1.0.0-rc.4",
          "vue-cli-plugin-quasar": "^0.17.1",
      

      I code in typescript btw, so in main.ts I had to change my
      import lang from 'quasar-framework/i18n/fr' into import lang from '../node_modules/quasar/lang/fr.js' because otherwise it wouldn’t find “quasar”. Same problem for other imports from “quasar”, yet it seems to work to import from “quasar-extras”. WTF?
      After hacking around like this the page displays something again but the style is completely broken, and components which used to work just fine don’t, with such warnings: Unknown custom element: <q-modal>. I followed the upgrade guide and probably fucked up somewhere, but to such an extent?

      1 Reply Last reply Reply Quote 0
      • metalsadman
        metalsadman last edited by

        @Cochonours Qmodal is QDialog / q-dialog in v1.

        1 Reply Last reply Reply Quote 1
        • C
          Cochonours last edited by Cochonours

          Oh, that solves it. Also q-layout-header is just q-header now. Do you know why my imports are broken though? I shouldn’t have to relatively specify the path…

          And also, the style is KO. I get no errors so I’m not sure how to solve the mess… Even my router-link’s are unclickable. <= nevermind that, I found the culprit.

          1 Reply Last reply Reply Quote 0
          • metalsadman
            metalsadman last edited by

            I suggest you follow the upgrade guide https://quasar.dev/start/upgrade-guide if you haven’t yet.

            1 Reply Last reply Reply Quote 0
            • C
              Cochonours last edited by

              That’s what I followed…

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