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 and webpack-bundle-tracker

    Help
    2
    3
    295
    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
      jmpmcmanus last edited by

      I’m trying to use webpack-bundle-tracker with quasar. I use extendWebpack, in my quasar.conf.js file, to run BundleTracker, which works (shown below). But the file it produces does not contain the publicPath I set in quasar.conf.js. webpack-bundle-tracker works with vue and the normal webpack config files. Has anybody tried using webpack-bundle-tracker with quasar, and found a solution?

      extendWebpack (cfg) {
      cfg.plugins.push(
      new BundleTracker({filename: ‘…/webpack-stats.json’})
      ),
      cfg.module.rules.push({
      enforce: ‘pre’,
      test: /.(js|vue)$/,
      loader: ‘eslint-loader’,
      exclude: /node_modules/,
      options: {
      formatter: require(‘eslint’).CLIEngine.getFormatter(‘stylish’)
      }
      })
      }

      1 Reply Last reply Reply Quote 0
      • J
        jmpmcmanus last edited by

        I found that I did not need to use this method.

        1 Reply Last reply Reply Quote 0
        • I
          iamsavinay last edited by iamsavinay

          Add publicpath: "http://localhost:8080/" in the arguments… now it works

          extendWebpack(cfg) {
          cfg.plugins.push(
          new BundleTracker({
          filename: “webpack-stats.json”,
          publicPath: “http://localhost:8080/”
          })
          ),
          cfg.module.rules.push({
          enforce: “pre”,
          test: /.(js|vue)$/,
          loader: “eslint-loader”,
          exclude: /node_modules/,
          options: {
          formatter: require(“eslint”).CLIEngine.getFormatter(“stylish”)
          }
          });
          }

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