Closed steveatkoan closed 1 year ago
Issue got duplicated at #14589 with similar fix. For those reading this and awaiting the PR, there is a workaround to set the config to true
, which will get passed through to vite and generate separate sourcemaps
For those who follow: I used a SourceMap
header as a workaround https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/#verify-sourcemappingurl-is-present
i am trying to do the same and cant quite figure it out, can you help show me what to do in my quasar.config file ? @steveatkoan
What happened?
I want to generate separate .map files for sentry.io When I edit quasar.config.js and set build.sourcemap = true i get 'inline' maps because https://github.com/quasarframework/quasar/blob/dev/app-vite/lib/config-tools.js#L120 sets
true
to'inline'
. The documentation says I can usetrue | 'inline' | 'hidden'
. I want the behaviour oftrue
but cannot get itI want to use source maps in production. Inline sourcemaps triple the size of each file, which make the download size a bit large for users. I'd prefer to use linked sourcemaps
What did you expect to happen?
as above. I want separate .map files for sentry but there is no way to configure quasar to generate them: my choices are none, hidden or inline
Reproduction URL
https://stackblitz.com/edit/quasarframework-wiiirz?file=quasar.config.js
How to reproduce?
install new quasar app edit quasar.config.ts set build.sourcemap = true run quasar build on the command line expect to see separate .map files actually see larger .js files with inline source maps
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite), SPA Mode
Platforms/Browsers
Chrome
Quasar info output
Relevant log output
No response
Additional context
No response