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

    Webpack alias doesn't seem to be working

    Help
    2
    4
    572
    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.
    • E
      emobe last edited by

      I added the config below to quasar config as specified on the docs and cli is saying it cannot find these aliases. It’s worked for me previously but in this project it isn’t working. I’m very stumped, is my config correct?

          cfg.resolve.alias = {
            ...cfg.resolve.alias,
      
            components: path.resolve(__dirname, "./src/components"),
            api: path.resolve(__dirname, "./src/api"),
            store: path.resolve(__dirname, "./src/store")
          };
      metalsadman 1 Reply Last reply Reply Quote 0
      • metalsadman
        metalsadman @emobe last edited by metalsadman

        @emobe looks good unless thats not on the proper quasar.conf.js>build prop, https://quasar.dev/quasar-cli/handling-webpack#Adding-Webpack-aliases

        E 1 Reply Last reply Reply Quote 0
        • E
          emobe @metalsadman last edited by

          @metalsadman jeez that was the problem. It was in electron and not build. Didn’t even think to check that, thanks a lot 😃

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

            @emobe docs is awesome, i always have a tab open :).

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