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

    SassError: File to import not found or unreadable: ~quasar-variables-styl.

    Help
    4
    6
    1672
    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.
    • T
      tarkhil last edited by

      quasar 1.42
      application made from scratch, not even a line of my code (yet)

      webpack --mode=development yields an error

      ERROR in ./src/styles/quasar.sass (./node_modules/css-loader/dist/cjs.js!./node_modules/sass-loader/dist/cjs.js!./src/styles/quasar.sass)
      Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
      SassError: File to import not found or unreadable: ~quasar-variables-styl.
              on line 15 of src/styles/quasar.variables.sass
              from line 1 of /home/tarkhil/order221/order221/src/styles/quasar.sass
      >> @import '~quasar-variables-styl';
      

      What should I fix?

      dobbel 1 Reply Last reply Reply Quote 0
      • dobbel
        dobbel @tarkhil last edited by

        @tarkhil

        what’s the output of quasar info ?

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

          @import '~quasar-variables-styl'
          This doesn’t even make sense inside a sass file
          I wonder if during the install, something botched

          T 1 Reply Last reply Reply Quote 0
          • T
            tarkhil @Hawkeye64 last edited by

            @Hawkeye64 got it, thanks

            beets 1 Reply Last reply Reply Quote 0
            • beets
              beets @tarkhil last edited by

              Hi @tarkhil, it helps to put how you resolved the issue just in case anyone else stumbles across this issue!

              1 Reply Last reply Reply Quote 1
              • T
                tarkhil last edited by

                Yes, it helped. Just removing those directives fixed the issue.

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