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

    Build cache issue

    Framework
    2
    2
    1521
    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.
    • H
      hexillion last edited by

      I usually build for prod locally using

      quasar build -m ssr
      

      I just noticed a bug where some old configuration ( some old constant values) still present in the final build output. I could not reproduce the issue locally as it happens only in the prod server. I found that the terser cache is not clear and had been stale for many builds e.g. paths

      node_modules/.cache/terser-webpack-plugin/content-v2/sha512/57/35/70a7c3ce0b9687dd572f83d6adf9c46a9107ff7c13ac4f514a9caeeacfd397f61169b8d91eb989142a33c84dbe6307997b5c75ba9c45bdd5584ec7a331a6
      

      Finally found out using grep that these files contained stale data and somehow become part of the build. I fixed my issue by clearing node modules folder. Want to know if this is common or we can do something to clear this on new builds.

      Thanks

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

        @hexillion

        you could try quasar clean before a build.

        https://quasar.dev/quasar-cli/commands-list#Clean

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