build: add flag for source maps in production (for upload)

Is your feature request related to a problem? Please describe. If I am was searching right, there currently is no way to instruct the build to generate source maps e.g. for uploading to Sentry. I am trying to workaround this via quasar build -d && upload.sh && quasar build

Describe the solution you’d like SOURCE_MAPS=true quasar build or quasar build --source-maps based on the strategy in the conf.

Describe alternatives you’ve considered

Additional context

[lmm-git]

We are using a self-implemented fix by extending the webpack config to achieve a similar behavior like requested for Sentry integration. Would be nice if this could get officially supported.

// extendWebpack  in quasar.conf

if (process.env.SOURCE_MAPS === 'yes') {
  const sourceMapPlugin = new webpack.SourceMapDevToolPlugin({
    filename: 'sourcemaps/[file].map'
  })
  cfg.plugins.push(sourceMapPlugin)
}

// Create sentry release only in CI
if (process.env.SENTRY_UPLOAD === 'yes') {
  const SentryWebpackPlugin = require('@sentry/webpack-plugin')
  // eslint-disable-next-line @typescript-eslint/no-unsafe-assignment
  const sentryPluginInstance = new SentryWebpackPlugin({
    // sentry-cli configuration
    authToken: process.env.SENTRY_WEBPACK_AUTH_TOKEN,
    org: 'our_org',
    project: 'our_project',
    url: 'https://sentry.our.domain',
    // eslint-disable-next-line @typescript-eslint/restrict-template-expressions
    release: process.env.RELEASE_NAME,
    stripCommonPrefix: true,
    rewrite: true,

    // webpack specific configuration
    include: cfg.output.path,
    ignore: ['node_modules', 'webpack.config.js', 'tests']
  })
  cfg.plugins.push(sentryPluginInstance)
}

The workaround @eljefedelrodeodeljefe described does not work for us as there are some changes to the source code/maps which make debugging hard when building it twice.

[hawkeye64]

I am closing this (again) but tagging @rstoenescu to see if it should be reopened.