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

    Unknown custom element: <q-input> - did you register the component correctly? For recursive

    Help
    5
    10
    6895
    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
      jeimz173 last edited by

      hi i am having trouble should i still import some quasar components here please help me thank you!

      1 Reply Last reply Reply Quote 0
      • rstoenescu
        rstoenescu Admin last edited by

        Yes. You need to import the components that you use. See http://quasar-framework.org/components/introduction-for-beginners.html#Using-Quasar-Components

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

          Hello, I have the same issue.
          This is what I did :

          import { QInput } from 'quasar';
            export default {
              components: {
                QInput,
              },
          

          But I still get: [Vue warn]: Unknown custom element: <q-input> - did you register the component correctly? For recursive components, make sure to provide the "name" option.

          Please help

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

            Try importing them in your main.js

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

              Thanks for your response @a47ae , but same result …

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

                Hm strange, your code looks okay to me. Did you change any other things?

                alexandre_c 1 Reply Last reply Reply Quote 0
                • alexandre_c
                  alexandre_c @a47ae last edited by

                  @a47ae No nothing else, could you try to use q-input on your side please ?

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

                    @rstoenescu Do you have an idea? I kinda stuck over here

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

                      @alexandre_c I am using it since beta and it works just fine, so definitely a problem in your setup 😕

                      1 Reply Last reply Reply Quote 0
                      • B
                        boolow5 last edited by

                        I fixed it in quasar.conf.js by setting the all option to auto, as below:
                        …
                        // Possible values for “all”:
                        // * ‘auto’ - Auto-import needed Quasar components & directives
                        // (slightly higher compile time; next to minimum bundle size; most convenient)
                        // * false - Manually specify what to import
                        // (fastest compile time; minimum bundle size; most tedious)
                        // * true - Import everything from Quasar
                        // (not treeshaking Quasar; biggest bundle size; convenient)
                        all: ‘auto’,
                        …

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