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

    Quasar build - file timestamps

    Framework
    3
    6
    1926
    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.
    • G
      glittle last edited by

      After running Quasar build, all the files in the “dist” folder have new timestamps on them. Is there any way to tell the builder to retain the original file’s timestamp?

      If I have a static image that doesn’t change, it should not have a new timestamp every time the project is built!

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

        There’s currently no way to avoid this other than manually uploading and not overriding /statics folder. The statics folder gets copied over to dist on each build. Will think of a way to only copy it if something indeed changed in the statics folder.

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

          Referencing https://github.com/quasarframework/quasar-template-default/issues/16

          1 Reply Last reply Reply Quote 0
          • G
            glittle last edited by

            This is especially a problem with the “vendor.js” file. When I make a small tweak to some wording in my site, the user has to re-download this massive file, even though it did not change at all!

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

              @glittle That’s why there’s a manifest.js file getting created there. That won’t change 😉 It’s part of the smart code-splitting strategy I wrote in the default Quasar template.

              1 Reply Last reply Reply Quote 0
              • S
                Sfinx last edited by

                I’m using the constant ‘watch’ based build which do not changes unneeded files.

                …package.json…
                scripts: {
                “watch”: “WATCH=true node build/script.build.js”,
                …
                …build/webpack.prod.conf.js…
                var watching = process.env.WATCH;

                var webpackConfig = merge(baseWebpackConfig, {
                watch: watching ? true : false,
                …

                and launch ‘npm run watch’ process. So any new file upload will initiate the incremental build. So such build is faster because of this.

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